From: Jonathan Nieder <jrnieder@gmail.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: GitList <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] doc: format-patch: don't use origin as a branch name
Date: Fri, 1 Aug 2014 12:36:14 -0700 [thread overview]
Message-ID: <20140801193614.GR12427@google.com> (raw)
In-Reply-To: <1406920826-4680-1-git-send-email-philipoakley@iee.org>
Philip Oakley wrote:
> Historically (5 Nov 2005 v0.99.9-46-g28ffb89) the git-format-patch used
> 'origin' as the upstream branch name. This is now used to name the remote.
> Use the more modern 'master' as the branch name.
Would 'origin/master' make sense?
Thanks,
Jonathan
next prev parent reply other threads:[~2014-08-01 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 19:20 [PATCH] doc: format-patch: don't use origin as a branch name Philip Oakley
2014-08-01 19:36 ` Jonathan Nieder [this message]
2014-08-01 20:08 ` Junio C Hamano
2014-08-01 22:26 ` Philip Oakley
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=20140801193614.GR12427@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philipoakley@iee.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.