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

Re: Feature Proposal: Track all branches from a given remote

From
Scott Johnson <jaywir3@gmail.com>
Date
Oct 26, 2014, 09:57 UTC
Message-ID
<CAEFop40qOPaq-6QrvNR0_MsgTv4K0jDNqb+m=BUZzFSXQ35YSQ@mail.gmail.com>
In-Reply-To
<20141026001610.GK312818@vauxhall.crustytoothpaste.net>
Hi Brian:
> [remote "origin"]
>   fetch = refs/heads/*:refs/heads/*

Yes, you're right, this works just fine as long as I move out from a branch that's not in the remote in question, for example by doing:

git checkout -b nothing git fetch

- OR -
git pull

Do you think there would be any interest in a patch that added this as a simple command line option, though? I guess the idea of this patch then would simply change this line in the .git/config file for the length of the operation (and specified remote), execute the git pull command, and then reset the configuration after the command finished. (There really wouldn't be a need to affect the configuration on the filesystem - simply the effective configuration used while git is running for this operation).

Thanks,
~Scott
Previous: brian m. carlsonNext: Andreas Schwab
Message 3 of 4 in “Feature Proposal: Track all branches from a given remote”
  1. Scott JohnsonOct 25, 2014
  2. brian m. carlsonOct 26, 2014
  3. Scott JohnsonOct 26, 2014
  4. Andreas SchwabOct 26, 2014

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.