From: Krzesimir Nowak <krzesimir@endocode.com>
To: git@vger.kernel.org
Cc: Krzesimir Nowak <krzesimir@endocode.com>
Subject: [RFC] make --set-upstream work for local branches not in refs/heads
Date: Tue, 4 Mar 2014 15:07:25 +0100 [thread overview]
Message-ID: <1393942046-11488-1-git-send-email-krzesimir@endocode.com> (raw)
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 reply other threads:[~2014-03-04 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 14:07 Krzesimir Nowak [this message]
2014-03-04 14:07 ` [PATCH] RFC: make --set-upstream work for branches not in refs/heads/ Krzesimir Nowak
2014-03-04 19:44 ` [RFC] make --set-upstream work for local branches not in refs/heads Junio C Hamano
2014-03-06 9:27 ` Krzesimir Nowak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1393942046-11488-1-git-send-email-krzesimir@endocode.com \
--to=krzesimir@endocode.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).