From: "Vincent Legoll" <vincent.legoll@gmail.com>
To: git@vger.kernel.org
Subject: git-diff & cg-diff behavior difference
Date: Sun, 17 Dec 2006 18:11:35 +0100 [thread overview]
Message-ID: <4727185d0612170911l52fab839x694399db729fd62d@mail.gmail.com> (raw)
I did not find something relevant in the docs, so I'll ask here.
git-diff works from everywhere in the tree, whereas cg-diff
does not, is that intentional ?
steps to reproduce:
--------------------
mkdir tmp
cd tmp
touch titi.txt
mkdir tutu
touch tutu/toto.txt
cg-init -I
cg-add -r .
cg-commit -C -m INIT
echo "tata" > titi.txt
git-diff
cg-diff
cd tutu
git-diff
cg-diff
--------------------
The 2 git-diff & 1st cg-diff outputs are the same, whereas the 2nd
cg-diff one is empty...
Quite a minor thing, but this could be added in the cg-diff man-page as a
difference of behavior.
--
next reply other threads:[~2006-12-17 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 17:11 Vincent Legoll [this message]
[not found] ` <46a038f90612181249y5ee69a8al28e97a22dca80c81@mail.gmail.com>
2006-12-19 10:33 ` git-diff & cg-diff behavior difference Vincent Legoll
2006-12-19 10:43 ` Vincent Legoll
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4727185d0612170911l52fab839x694399db729fd62d@mail.gmail.com \
--to=vincent.legoll@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).