From: Jay Soffian <jaysoffian@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: rev-parse vs. rev-list --no-walk
Date: Mon, 3 May 2010 11:22:40 -0400 [thread overview]
Message-ID: <t2z76718491005030822l469c720ag1466ecd2bad31f32@mail.gmail.com> (raw)
In-Reply-To: <7v1vdv4ccz.fsf@alter.siamese.dyndns.org>
On Sat, May 1, 2010 at 4:05 PM, Junio C Hamano <gitster@pobox.com> wrote:
> I think one sane thing to do is to stop adding new rev-flags revision.c
> supports to rev-parse (it already lags behind and nobody complained that
> rev-parse doesn't understand --first-parent as a rev-flag), and keep its
> use as "revision and non revision option sifter" only to support older
> scripts written back in v1.0.0 days. Its primary use these days is "turn
> symbolic object names into 40-letter SHA-1", but "option sifter" aspect of
> the command seems to have outlived its usefulness.
We tell scripters to be careful to use the plumbing and not the
porcelain. From that standpoint, shouldn't we do our best to prevent
the plumbing from falling into disrepair?
(Or perhaps I'm reading too much into what you say.)
j.
next prev parent reply other threads:[~2010-05-03 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 18:35 rev-parse vs. rev-list --no-walk Michael J Gruber
2010-05-01 20:05 ` Junio C Hamano
2010-05-03 15:22 ` Jay Soffian [this message]
2010-05-03 15:50 ` Michael J Gruber
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=t2z76718491005030822l469c720ag1466ecd2bad31f32@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).