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

Re: [PATCH] describe: Add --left-only option

From
Mike Crowe <mac@mcrowe.com>
Date
May 17, 2013, 15:16 UTC
Message-ID
<20130517151623.GA3083@mcrowe.com>
In-Reply-To
<20130517150329.GA27005@serenity.lan>
On Fri, May 17, 2013 at 04:03:29PM +0100, John Keeping wrote:
Show 9 quoted lines
> On Fri, May 17, 2013 at 03:24:26PM +0100, Mike Crowe wrote:
> > Only consider the first parent commit when walking the commit history. This
> > is useful if you only wish to match tags on your branch after a merge.
> 
> For consistency with "git log" should this be called "--first-parent"?
> 
> In "git log" --left-only takes effect only when considering a symmetric
> range, which "git describe" isn't.  Whereas --first-parent triggers
> precisely the behaviour described here.
I think you're right.
I'm happy to rename it and resubmit if the rest of the patch passes muster.
Thanks.
Mike.
Previous: John Keeping
Message 3 of 3 in “describe: Add --left-only option”
  1. describe: Add --left-only optionMike Crowe, May 17, 2013
  2. John KeepingMay 17, 2013
  3. Mike CroweMay 17, 2013

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.