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

Re: [PATCH 0/5] fetch & co: misc output cleanup

From
SSanti <sbejar@gmail.com>
Date
Sep 29, 2006, 20:48 UTC
Message-ID
<8aa486160609291348m411932aqfd1049c96ed624df@mail.gmail.com>
In-Reply-To
<451D6BDB.50900@gmail.com>
2006/9/29, A Large Angry SCM <gitzilla@gmail.com>:
Show 13 quoted lines
> Santi Béjar wrote:
> > this patchset includes:
> >
> >       fetch: Reset remote refs list each time fetch_main is called
> >       fetch & co: Use "hash1..hash2" instead of "from hash1 to hash2"
> >       fetch & co: Use short sha1 in the output
> >       fetch: Add output for the not fast forward case
> >       fetch: Clean output
>
> Please do not make short ID output the default. That is, unless you can
> somehow guarantee that the short ID reported today will _always_ be
> unambiguous even with future additions to the repository.
>

There is not such guarantee. But the fetch output is to be use immediately in git-log, etc. If you want these "guarantees" you must know that you have to keep the long version.

By the way, is there a way to show all the commits,tags,... that abbreviate to a short hash? This way instead of just saying "bad revision" we could show the list of possible revisions.

Also, git-log & co also output abbreviated hashes by default. So why not for git-fetch?

Santi
Previous: A Large Angry SCMNext: Junio C Hamano
Message 11 of 12 in “fetch & co: misc output cleanup”
  1. 0/5 fetch & co: misc output cleanupSanti Béjar, Sep 29, 2006
  2. 1/5 fetch: Reset remote refs list each time fetch_main is calledSanti Béjar, Sep 29, 2006
  3. 2/5 fetch & co: Use "hash1..hash2" instead of "from hash1 to hash2"Santi Béjar, Sep 29, 2006
  4. 3/5 fetch & co: Use short sha1 in the outputSanti Béjar, Sep 29, 2006
  5. 4/5 fetch: Add output for the not fast forward caseSanti Béjar, Sep 29, 2006
  6. 5/5 fetch: Clean outputSanti Béjar, Sep 29, 2006
  7. Junio C HamanoSep 30, 2006
  8. SantiSep 30, 2006
  9. Junio C HamanoSep 30, 2006
  10. A Large Angry SCMSep 29, 2006
  11. SantiSep 29, 2006
  12. Junio C HamanoSep 29, 2006

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.