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

[RFC] make --set-upstream work for local branches not in refs/heads

From
Krzesimir Nowak <krzesimir@endocode.com>
Date
Mar 4, 2014, 14:07 UTC
Message-ID
<1393942046-11488-1-git-send-email-krzesimir@endocode.com>

It might be possible (in "Gerrited" setups) to have local branches outside refs/heads/, like for example in following fetch config:

[remote "origin"]
	url = ssh://user@example.com/my-project
	fetch = +refs/heads/*:refs/remotes/origin/*
	fetch = +refs/wip/*:refs/remotes/origin-wip/*

Let's say that 'test' branch already exist in origin/refs/wip/. If I call:

git checkout test
then it will create a new branch and add an entry to .git/config:
[branch "test"]
	remote = origin
	merge = refs/wip/test
But if I create a branch 'test2' and call:
git push --set-upstream origin test2:refs/wip/test2

then branch is pushed, but no entry in .git config is created. I have to do it manually. I attached a hack-patch to have it working just to check with you if anything like that would be accepted. Obviously the get_local_refs() would need to compute the actual list of local hierarchies (if it is possible at all). And it probably should get a better name. And probably something else.

What do you think?
Krzesimir Nowak (1):
  RFC: make --set-upstream work for branches not in refs/heads/
 transport.c | 41 ++++++++++++++++++++++++++++++++++-------
 1 file changed, 34 insertions(+), 7 deletions(-)
-- 
1.8.3.1
Next: Krzesimir Nowak
Message 1 of 4 in “[RFC] make --set-upstream work for local branches not in refs/heads”
  1. Krzesimir NowakMar 4, 2014
  2. RFC: make --set-upstream work for branches not in refs/heads/Krzesimir Nowak, Mar 4, 2014
  3. Junio C HamanoMar 4, 2014
  4. Krzesimir NowakMar 6, 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.