Re: git-diff & cg-diff behavior difference
- From
- Vincent Legoll <vincent.legoll@gmail.com>
- Date
- Dec 19, 2006, 10:33 UTC
- Message-ID
- <4727185d0612190233w26188a56t50ad49d2de58b88b@mail.gmail.com>
- In-Reply-To
- <46a038f90612181249y5ee69a8al28e97a22dca80c81@mail.gmail.com>
On 12/18/06, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> I'd say that it's a bug that cg-diff doesn't work in a subdir. > However, there is a much more important difference between cg-diff and > git-diff: cg-diff is equivalent to git-diff HEAD because cogito hides > the index from you.
That's what I wanted to know: if it was a deliberate behavior, a bug on my side, or on git's...
> If you are developing in a (mostly) straight line, and not dealing > much with merges and rebases, that's a great simplification. If you > are coming from a different SCM it's probably a good thing too.
That's me and me !
> If/when you want to use git's smarts for merging and rebasing, you'll > definitely want to know a lot more about the index, and you'll > probably stop using cogito.
That will be me some times...
> (Actually, even though I know and love the index I use cogito all the > time, and switch to git commands for merging and rebasing. Works > great... and yet Linus is in a merge-centric role, so changing the > defaults to ignore the index most of the time is a bit of a hot issue
That's no problem with me, if behavior is properly documented...