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

Re: [PATCH] Per branch properties for pull and fetch

From
Martin Waitz <tali@admingilde.org>
Date
Jul 27, 2006, 12:02 UTC
Message-ID
<20060727120220.GD27593@admingilde.org>
In-Reply-To
<8aa486160607270306s3f49a01cq91ef61e2c9f005e@mail.gmail.com>
hoi :)
On Thu, Jul 27, 2006 at 12:06:34PM +0200, Santi wrote:
> >> could we default the to-be-merged branch to "remotes/$remote/$branch" if
> >> that exists?. That could make life a lot easier when using
> >> clone --use-separate-remote.
> On the other hand, my patch changes the behaviour only when explicitly
> configured, and your proposed default would change the behaviour even
> without changes to the config.
that is correct.

The current default is to always use the remote's master branch, right? What do others think: does it make sense to default to the same branchname on the remote side?

It could make life a bit easier if you want to synchronize several topic branches between different sites.

-- 
Martin Waitz
Previous: SantiNext: Santi
Message 5 of 7 in “Per branch properties for pull and fetch”
  1. Per branch properties for pull and fetchSanti Béjar, Jul 27, 2006
  2. Martin WaitzJul 27, 2006
  3. SantiJul 27, 2006
  4. SantiJul 27, 2006
  5. Martin WaitzJul 27, 2006
  6. SantiJul 27, 2006
  7. Matthias LederhoferJul 27, 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.