Matthieu Moy wrote:
quoted text > Andreas Ericsson <ae@op5.se> writes:
>
>> What about
>>
>> 3) getting the repo with all the history while still not having to be
>> online to actually commit to *your* copy of the repo. When you later
>> get online, you can send all your changes in a big hunk, or let bazaar
>> email them to the maintainer as patches, or...
>
> Well, the discussion was about checkouts, so I was talking about
> checkouts ;-).
>
Differences in nomenclature is really messing this discussion up. In
git, a "checkout" is the act of pulling objects from the object database
into the working tree. I.e., the act of "clothing" a "bare" repository.
quoted text >> but the ability to commit to whatever branch I like in my local repo
>> and then just send the diffs by email or please-pull requests to
>> upstream authors is what makes git work so well for me.
>
> Sure. Once again, Bazaar does it this way too. There's an _additional
> feature_ called checkout which allows you to work in another way,
> though. As most "feature", it's not useful to everybody.
>
Now I'm really confused. Does bazaar have both "clone" (git-style
fetching a full repo and all the branches) and "checkout" (cvs-style
fetching only the working tree)?
quoted text >
>> Side-note 2: Three really great things that have made work a lot
>> easier and more enjoyable since we changed from cvs to git and that
>> aren't mentioned in the comparison table:
>
> Sure. And regarding this, hopufully, most modern VCS go in the same
> direction.
>
>> * Dependency/history graph display tools
