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

Re: git name-rev not accepting abbreviated SHA with --stdin

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Jun 25, 2015, 02:01 UTC
Message-ID
<558B60E4.9020604@gmail.com>
In-Reply-To
<xmqqsi9g8x51.fsf@gitster.dls.corp.google.com>
On 06/25/2015 05:41 AM, Junio C Hamano wrote:
Show 8 quoted lines
> Sitaram Chamarty <sitaramc@gmail.com> writes:
> 
>> This *is* documented, but I'm curious why this distinction is made.
> 
> I think it is from mere laziness, and also in a smaller degree
> coming from an expectation that --stdin would be fed by another
> script like rev-list where feeding full 40-hex is less work than
> feeding unique abbreviated prefix.

Makes sense; thanks. Maybe if I feel really adventurous I will, one day, look at the code :-)

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “git name-rev not accepting abbreviated SHA with --stdin”
  1. Sitaram ChamartyJun 24, 2015
  2. Junio C HamanoJun 25, 2015
  3. Sitaram ChamartyJun 25, 2015
  4. Junio C HamanoJul 3, 2015
  5. Sitaram ChamartyJul 4, 2015
  6. Junio C HamanoJul 4, 2015

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.