On Mon, Aug 22, 2005 at 14:55:50 +0200, Aldrik KLEBER wrote: > > Also, I often end up making a mess of my repository and would like > > to be able to commit revisions by cherry-picking changes/hunks. > > darcs does this very nicely. > > > tla and baz too, this is a natural way of working. > In my case I use to make a snapshot branch wich contain only the revisions I > want and not the others. > > baz branch dev-branch--0.1--patch-5 snap-branch--0.1 > baz branch dev-branch--0.1--patch-8 snap-branch--0.1 > baz branch dev-branch--0.1--patch-35 snap-branch--0.1 > > and next snap-branch contains revisions 5, 8, 35
That's all good and well, but it relies on revisions on dev-branch being
clean.
> > So if I made two changes to a file, I can commit once and select
> > only the first hunk, then commit again and let it write the second
> > hunk to the archive.
> you can commit
> _ the full tree : baz commit
> _ a set of file: baz commit file1 file2 file3
> or baz commit --file-list list_of_file_to_commit.txt
> _ just a file : baz commit file1
But that's not a *HUNK* granularity. *HUNK* granularity means being able to
commit just a *part* of single file -- bazaar, nor most other version control
systems just are not there.
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <[EMAIL
PROTECTED]>
signature.asc
Description: Digital signature
_______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
