From: Tony Luck <tony.luck@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: tony.luck@intel.com, git@vger.kernel.org,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: deprecating more
Date: Fri, 16 Sep 2005 23:13:09 -0700 [thread overview]
Message-ID: <12c511ca05091623135ccbcae1@mail.gmail.com> (raw)
In-Reply-To: <7vfys4e003.fsf@assigned-by-dhcp.cox.net>
> 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.
Sure ... I'll be glad to see git-rev-tree go. For some reason it got wired
into my fingers early on, and I keep typing it when I mean to use
git-rev-list, then stare at the screen all confused when it complains
about the arguments I gave it.
-Tony
prev parent reply other threads:[~2005-09-17 6:13 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
2005-09-17 6:13 ` Tony Luck [this message]
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=12c511ca05091623135ccbcae1@mail.gmail.com \
--to=tony.luck@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).