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

Re: [PATCH] New script: git-changelog.perl - revised

From
Alex Riesen <raa.lkml@gmail.com>
Date
Nov 3, 2007, 14:58 UTC
Message-ID
<20071103145848.GA3175@steel.home>
In-Reply-To
<67837cd60711030646p6d7dc8e3t8a5f5f336e8bbad6@mail.gmail.com>
Ronald Landheer-Cieslak, Sat, Nov 03, 2007 14:46:27 +0100:
Show 13 quoted lines
> On Nov 3, 2007 4:36 AM, Andreas Ericsson <ae@op5.se> wrote:
> > Ronald Landheer-Cieslak wrote:
> > >
> > > This is also available through git at
> > > git://vlinder.landheer-cieslak.com/git/git.git#topic/git-log-changelog
> > >
> >
> > This mode of specifying a repository + branch was just thoroughly shot
> > down in a list discussion, and git certainly doesn't grok it. I'd be a
> > happier fella if you didn't use it.
> >
> Is there a canonical way to specify both the location and the branch
> in one shot, then? ...
Something like this:
    Please fetch from
    git://vlinder.landheer-cieslak.com/git/git.git topic/git-log-changelog

If one uses git-fetch the result will be in FETCH_HEAD, a pull will merge it nicely with the commit message like:

    "Merge branch 'topic/git-log-changelog' of git://vlinder.landheer-cieslak.com/git/git"
which fits, I believe.
Previous: Johannes Schindelin
Message 5 of 5 in “New script: git-changelog.perl - revised”
  1. New script: git-changelog.perl - revisedRonald Landheer-Cieslak, Nov 2, 2007
  2. Andreas EricssonNov 3, 2007
  3. Ronald Landheer-CieslakNov 3, 2007
  4. Johannes SchindelinNov 3, 2007
  5. Alex RiesenNov 3, 2007

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.