From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: branch.<name>.merge specifying remote branch name
Date: Sat, 23 Dec 2006 10:14:49 +0100 [thread overview]
Message-ID: <emirt5$kh3$2@sea.gmane.org> (raw)
About the discussion about branch.<name>.merge specifying remote branch name
and relative merits of specifying remote branch name (without need for
tracking branch), and local branch name (which is supposedly more user
friendly, and branch name specifies also remote usually)...
Perhaps it is time to resurrect branch.<name>.mergeLocal (or localMerge)
idea, and both sides would be happy (well, at least when one would code
it ;-).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next reply other threads:[~2006-12-23 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-23 9:14 Jakub Narebski [this message]
2006-12-23 14:26 ` branch.<name>.merge specifying remote branch name Nicolas Pitre
2006-12-23 14:32 ` Jakub Narebski
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='emirt5$kh3$2@sea.gmane.org' \
--to=jnareb@gmail.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).