From: Joao Eduardo Luis <joao@suse.de>
To: Ken Dreyer <kdreyer@redhat.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Merging PRs on the command line
Date: Wed, 13 May 2015 10:13:00 +0100 [thread overview]
Message-ID: <5553159C.3070607@suse.de> (raw)
In-Reply-To: <55527771.6060401@redhat.com>
On 05/12/2015 10:58 PM, Ken Dreyer wrote:
> The thing that sold me on this is that all the merge commits are
> authored by "kdreyer@redhat.com" instead of my personal email address. I
> found that when I clicked the "Merge" button in GitHub's web UI, the
> merge commits were authored by my primary email address for my
> "ktdreyer" GitHub UID, which isn't really what I want for Ceph.
I thought this was solved by setting a secondary email as the
organization's default email, but now I see how wrong I was. Merge
commits do go with my primary :(
-Joao
prev parent reply other threads:[~2015-05-13 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 21:58 Merging PRs on the command line Ken Dreyer
2015-05-12 22:00 ` Mark Nelson
2015-05-12 22:09 ` Loic Dachary
2015-05-13 9:13 ` Joao Eduardo Luis [this message]
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=5553159C.3070607@suse.de \
--to=joao@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=kdreyer@redhat.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 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.