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

Re: [PATCH 3/3] fetch: optionally store the current remote information in the config

From
Jakub Narebski <jnareb@gmail.com>
Date
Apr 30, 2006, 14:19 UTC
Message-ID
<e32h0o$15n$1@sea.gmane.org>
In-Reply-To
<Pine.LNX.4.63.0604301524080.2646@wbgn013.biozentrum.uni-wuerzburg.de>

There was thread about storing somewhere default branch we merge to during pull, instead of using always surrent one. Different schemes were proposed, most of them depending on the remotes configuration being available [also] in config file.

Perhaps it would be easiest to extend existing notation in the following
way: 
  <from>:<to>[:<merge>]

By the way: it would be nice to have command/script to trasform freely between 'remotes/' and config file.

P.S. I wonder if it would be difficult to implement 'include <file>' for config file...

-- 
Jakub Narebski
Warsaw, Poland
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 2 of 16 in “fetch: optionally store the current remote information in the config”
  1. 3/3 fetch: optionally store the current remote information in the configJohannes Schindelin, Apr 30, 2006
  2. Jakub NarebskiApr 30, 2006
  3. Johannes SchindelinApr 30, 2006
  4. Jakub NarebskiApr 30, 2006
  5. seanApr 30, 2006
  6. Johannes SchindelinApr 30, 2006
  7. seanApr 30, 2006
  8. Jakub NarebskiApr 30, 2006
  9. seanApr 30, 2006
  10. Jakub NarebskiApr 30, 2006
  11. Johannes SchindelinApr 30, 2006
  12. seanApr 30, 2006
  13. Junio C HamanoApr 30, 2006
  14. Junio C HamanoMay 2, 2006
  15. Johannes SchindelinMay 2, 2006
  16. Junio C HamanoMay 3, 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.