From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>, git@vger.kernel.org
Subject: Re: Random thoughts on "upstream"
Date: Sun, 19 May 2013 01:37:51 +0530 [thread overview]
Message-ID: <CALkWK0=0SwWW+LC3iPy=A9tLBOxrXgYH1cYNazrchv3_jU_oMg@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0kYKZGhthdrb6-7RD_c2A7E9rscAZU3=JHM-4rYre6w=Q@mail.gmail.com>
Ramkumar Ramachandra wrote:
> I guess what I'm saying is: refspec semantics are inherent properties
> of the remote, not of the local branch.
[remote "ram"]
push = refs/heads/link:refs/heads/for-junio/link
is saying: if the branch name matches "link", push it to for-junio/link.
[branch "link"]
push = refs/heads/for-junio/link
is saying: push _this_ branch to for-junio/link, irrespective of what
it is called.
An example illustrating this clearly:
# on branch link-v2
# work ...
$ git push
# work ...
# ok, I'm ready to replace link
$ git branch -M link
$ git push
# where should the push go?
Also: putting branch-specific configuration in remote.<name>.push
would mean that it can potentially accumulate a lot of cruft from
deleted branches. It's the same kind problem we face with .gitignore,
no?
next prev parent reply other threads:[~2013-05-18 20:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 17:55 Random thoughts on "upstream" Junio C Hamano
2013-05-16 23:03 ` Felipe Contreras
2013-05-16 23:17 ` Junio C Hamano
2013-05-17 0:00 ` Felipe Contreras
2013-05-17 1:31 ` Junio C Hamano
2013-05-17 1:59 ` Felipe Contreras
2013-05-17 2:00 ` Felipe Contreras
2013-05-17 12:43 ` Ramkumar Ramachandra
2013-05-17 16:45 ` Junio C Hamano
2013-05-17 17:01 ` Ramkumar Ramachandra
2013-05-17 17:51 ` Junio C Hamano
2013-05-18 18:27 ` Ramkumar Ramachandra
2013-05-18 20:07 ` Ramkumar Ramachandra [this message]
2013-05-18 22:36 ` Felipe Contreras
2013-05-18 22:33 ` Felipe Contreras
2013-05-19 5:58 ` Junio C Hamano
2013-05-19 11:44 ` Ramkumar Ramachandra
2013-05-19 11:48 ` Felipe Contreras
2013-05-19 11:54 ` Ramkumar Ramachandra
2013-05-19 12:00 ` Felipe Contreras
2013-05-20 4:28 ` Junio C Hamano
2013-05-23 10:42 ` Ramkumar Ramachandra
2013-05-23 10:53 ` Felipe Contreras
2013-05-23 17:25 ` Junio C Hamano
2013-05-23 17:41 ` Ramkumar Ramachandra
2013-05-24 6:39 ` Ramkumar Ramachandra
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='CALkWK0=0SwWW+LC3iPy=A9tLBOxrXgYH1cYNazrchv3_jU_oMg@mail.gmail.com' \
--to=artagnon@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).