From: Johannes Berg <johannes@sipsolutions.net>
To: santosh shilimkar <santosh.shilimkar@oracle.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [Odd commit author id merge via netdev]
Date: Fri, 01 Apr 2016 22:01:44 +0200 [thread overview]
Message-ID: <1459540904.3342.2.camel@sipsolutions.net> (raw)
In-Reply-To: <56FEB50E.4060004@oracle.com> (sfid-20160401_195127_367731_49036B1D)
On Fri, 2016-04-01 at 10:51 -0700, santosh shilimkar wrote:
> Hi Dave,
>
> I noticed something odd while checking the recent
> commits of mine in kernel.org tree made it via netdev.
>
> Don't know if its patchwork tool doing this.
> Usual author line in my git objects :
> Author: Santosh Shilimkar <emaid-id>
>
> But the commits going via your tree seems to be like below..
> Author: email-id <email-id>
>
> Few more examples of the commits end of the email. Can this
> be fixed for future commits ? The git objects you pulled from
> my tree directly have right author format where as ones which
> are picked from patchworks seems to be odd.
>
Patchwork does store this info somehow and re-use it, quite possibly
from the very first patch you ever sent. I think this bug was *just*
fixed in patchwork, but it'll probably be a while until that fix lands.
However, you can go and create a patchwork account with the real name,
associate it with all the email addresses you use and then I think
it'll pick it up. Not entirely sure though, you'll have to test it.
johannes
next prev parent reply other threads:[~2016-04-01 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 17:51 [Odd commit author id merge via netdev] santosh shilimkar
2016-04-01 20:01 ` Johannes Berg [this message]
2016-04-01 22:15 ` santosh shilimkar
2016-04-17 0:13 ` santosh shilimkar
2016-04-19 8:55 ` Johannes Berg
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=1459540904.3342.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@oracle.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).