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

Re: branch.<name>.merge specifying remote branch name

From
Nicolas Pitre <nico@cam.org>
Date
Dec 23, 2006, 14:26 UTC
Message-ID
<Pine.LNX.4.64.0612230924110.18171@xanadu.home>
In-Reply-To
<emirt5$kh3$2@sea.gmane.org>
On Sat, 23 Dec 2006, Jakub Narebski wrote:
Show 8 quoted lines
> About the discussion about branch.<name>.merge specifying remote branch name
> and relative merits of specifying remote branch name (without need for
> tracking branch), and local branch name (which is supposedly more user
> friendly, and branch name specifies also remote usually)...
> 
> Perhaps it is time to resurrect branch.<name>.mergeLocal (or localMerge)
> idea, and both sides would be happy (well, at least when one would code
> it ;-).
Adding more and more options doesn't make it friendlier to use.

Why couldn't both names (local and remote) be accepted by branch.blah.merge?

Nicolas
Previous: Jakub NarebskiNext: Jakub Narebski
Message 2 of 3 in “branch.<name>.merge specifying remote branch name”
  1. Jakub NarebskiDec 23, 2006
  2. Nicolas PitreDec 23, 2006
  3. Jakub NarebskiDec 23, 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.