Stephen Leake <[EMAIL PROTECTED]> writes:
> What do you see as the advantage?
For bzr, the nice thing is that the default output is both easy to
understand and short to read:
added:
bar
boz
renamed:
foo => foobar
You don't have to understand the meaning of letters (A for Added, and
so). So, it's easier for newbies than
A bar
A boz
R foo => foobar
and shorter than
added: bar
added: boz
renamed: foo => foobar
For git, there's something a bit different. Yes, a file can appear in
two sections of "git status", but this actually has a meaning:
$ echo 'one line' >> one
$ git add one
$ echo 'second line' >> one
$ git st
# On branch master
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# modified: one
#
# Changed but not updated:
# (use "git add <file>..." to update what will be committed)
#
# modified: one
#
Here, I have one staged change ("one line" added to file "one"), and
one unstaged change ("second line" in the same file). Git tells me
both (and if I have color.status set to true, the first one is green,
and the second red).
But Git is very particular here, with it's notion of index.
--
Matthieu
_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev
