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

Re: [PATCH] config.txt: update branch.<name>.merge documentation

From
Yann Dirson <ydirson@altern.org>
Date
Feb 3, 2007, 16:29 UTC
Message-ID
<20070203162949.GF4266@nan92-1-81-57-214-146.fbx.proxad.net>
In-Reply-To
<8aa486160702030819k24a42ac4w115b83980d3ee17e@mail.gmail.com>
On Sat, Feb 03, 2007 at 05:19:53PM +0100, Santi Béjar wrote:
Show 6 quoted lines
> >git-parser-remote also looks branch.*.merge with --get-all, so it is
> >interesting to know what happens for multiple values (if git-fetch
> >just marks them all, how does git-pull react ?).
> 
> The last sentence in the branch.<name>.merge says that it would
> produce an octopus, is this enough?
D'oh, right.
Previous: Santi BéjarNext: Santi Béjar
Message 4 of 6 in “config.txt: update branch.<name>.merge documentation”
  1. config.txt: update branch.<name>.merge documentationSanti Béjar, Feb 3, 2007
  2. Yann DirsonFeb 3, 2007
  3. Santi BéjarFeb 3, 2007
  4. Yann DirsonFeb 3, 2007
  5. Santi BéjarFeb 4, 2007
  6. Junio C HamanoFeb 4, 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.