From: Junio C Hamano <junkio@cox.net>
To: tony.luck@intel.com
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: deprecating more
Date: Fri, 16 Sep 2005 22:28:28 -0700 [thread overview]
Message-ID: <7vfys4e003.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0509161938580.26803@g5.osdl.org> (Linus Torvalds's message of "Fri, 16 Sep 2005 19:50:35 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> On Fri, 16 Sep 2005, Junio C Hamano wrote:
>
>> What do you think about the other commands I mentioned?
>
> I think they can all go. I think some old scripts migth still use
> git-rev-tree, but it really is clearly inferior in every way to
> git-rev-list that such scripts should be fixed anyway. Fixing them should
> be pretty easy.
I found one in our source. Tony, is the following change
acceptable to you?
------------
[PATCH] Use git-rev-list not git-rev-tree where appropriate.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
diff --git a/Documentation/howto/using-topic-branches.txt b/Documentation/howto/using-topic-branches.txt
--- a/Documentation/howto/using-topic-branches.txt
+++ b/Documentation/howto/using-topic-branches.txt
@@ -245,7 +245,7 @@ gb=$(tput setab 2)
rb=$(tput setab 1)
restore=$(tput setab 9)
-if [ `git-rev-tree release ^test | wc -c` -gt 0 ]
+if [ `git-rev-list release ^test | wc -c` -gt 0 ]
then
echo $rb Warning: commits in release that are not in test $restore
git-whatchanged release ^test
@@ -262,7 +262,7 @@ do
status=
for ref in test release linus
do
- if [ `git-rev-tree $branch ^$ref | wc -c` -gt 0 ]
+ if [ `git-rev-list $branch ^$ref | wc -c` -gt 0 ]
then
status=$status${ref:0:1}
fi
next prev parent reply other threads:[~2005-09-17 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 1:04 git-diff-stages? Junio C Hamano
2005-09-17 1:31 ` deprecating more Junio C Hamano
2005-09-17 1:58 ` Horst von Brand
2005-09-17 1:59 ` Linus Torvalds
2005-09-17 2:29 ` Junio C Hamano
2005-09-17 2:50 ` Linus Torvalds
2005-09-17 5:28 ` Junio C Hamano [this message]
2005-09-17 6:13 ` Tony Luck
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=7vfys4e003.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.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).