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

Re: [PATCH] Allow --pretty to be passed to git-describe.

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 25, 2014, 05:04 UTC
Message-ID
<7vy4zyoom2.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1395709444-11220-1-git-send-email-tipecaml@gmail.com>
Cyril Roelandt <tipecaml@gmail.com> writes:
> In some cases, ony may want to find the the most recent tag that is reachable
> from a commit and have it pretty printed, using the formatting options available
> in git-log and git-show.

Sorry, but I do not understand the motivation I can read from these three lines well enough to say that such a change makes any sense.

It somewhat sounds similar to adding a "--long" option to "git show" so that "git show --long v1.9.0" will act as if it were running a "git log v1.9.0". Yes, you can add any option to tell a command to do something that is usually considered to be a task for some other command, but does it even make sense to do so in the first place?

Previous: Cyril RoelandtNext: Eric Sunshine
Message 2 of 3 in “Allow --pretty to be passed to git-describe.”
  1. Allow --pretty to be passed to git-describe.Cyril Roelandt, Mar 25, 2014
  2. Junio C HamanoMar 25, 2014
  3. Eric SunshineMar 25, 2014

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.