git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: rev-parse vs. rev-list --no-walk

From
Jay Soffian <jaysoffian@gmail.com>
Date
May 3, 2010, 15:22 UTC
Message-ID
<t2z76718491005030822l469c720ag1466ecd2bad31f32@mail.gmail.com>
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:
Show 7 quoted lines
> 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.
Previous: Junio C HamanoNext: Michael J Gruber
Message 3 of 4 in “rev-parse vs. rev-list --no-walk”
  1. Michael J GruberMay 1, 2010
  2. Junio C HamanoMay 1, 2010
  3. Jay SoffianMay 3, 2010
  4. Michael J GruberMay 3, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.