On Sun, Oct 27, 2002 at 09:29:18PM +0100, Rafael Garcia-Suarez wrote:
> Peter Davis wrote:
> > > Have each repository setup with a post-commit hook that writes the
> > > diffs for that commit out to a file (like the commit-email.pl that we
> > > use on svn.collab.net). Then, when you need to sync, you apply the
> > > changes from, say, your laptop's repos to your desktop's working copy,
> > > and commit them up (and vice-versa).
> >
> > Is there a reason why the answer to distributed repositories is not as simple
> > as this? Could not Subversion (or somebody with some free time) provide an
> > "official" tool to create, manage, and apply such patches?
>
> A quick list of problems with traditional patches (i.e. diff(1) output)
> * metadata (properties)
> * log messages
> * binary files
> * deletion of directories
> * addition of empty files
> * platform-dependent line-endings (ie. with svn:eol-style=native)
> * svn cp
> Thus you'll need to add metadata in the output, and have the import
> program correctly interpret this. (but it'd be great!)
Well, why not have the post-commit script do a dump(head-1, head) and
save it into a file? That should be rich enough.
It might need a bit of fudging on import, if you commit something
before "resynching" but it should be doable.
Cheers,
florin
--
"If it's not broken, let's fix it till it is."
41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4
- application/pgp-signature attachment: stored
Received on Mon Oct 28 06:05:38 2002