public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: KY Srinivasan <kys@microsoft.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"apw@canonical.com" <apw@canonical.com>,
	"ben@decadent.org.uk" <ben@decadent.org.uk>,
	"thozza@redhat.com" <thozza@redhat.com>,
	"dcbw@redhat.com" <dcbw@redhat.com>
Subject: Re: [PATCH 0/4] Tools: hv
Date: Wed, 5 Sep 2012 12:38:52 -0700	[thread overview]
Message-ID: <20120905193852.GA412@kroah.com> (raw)
In-Reply-To: <426367E2313C2449837CD2DE46E7EAF9309E034B@SN2PRD0310MB382.namprd03.prod.outlook.com>

On Wed, Sep 05, 2012 at 07:24:37PM +0000, KY Srinivasan wrote:
> > On Wed, Sep 05, 2012 at 10:01:59AM -0700, K. Y. Srinivasan wrote:
> > > This patchset was authored by Ben Hutchings <ben@decadent.org.uk>. Ben
> > > asked me to submit this patchset. This patchset cleans up the KVP daemon
> > > code and fixes some bugs.
> > >
> > >
> > > K. Y. Srinivasan (4):
> > >   tools: hv: Fix file handle leak
> > >   tools: hv: Fix exit() error code
> > >   tools: hv: Check for read/write errors
> > >   tools: hv: Parse /etc/os-release
> > 
> > If Ben wrote these, why are you showing that you wrote them?
> 
> Ben asked me to apply these patches on the tip (of my tree) and send the
> patches out and that is what I did. I recreated these patches after applying to
> my tree and that is what I have sent out. How could I have made the authorship
> more clear (other than noting so in the comment which I have done).

You could have actually _kept_ the proper authorship information so that
git shows who wrote the patch.  As your shortlog shows above, it looks
like you wrote the patches, not Ben, which is not acceptable.

As to how to actually do that, well, I'll leave that as an exercise for
the reader (hint, we document how to do this quite well...)

greg k-h

  reply	other threads:[~2012-09-05 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 17:01 [PATCH 0/4] Tools: hv K. Y. Srinivasan
2012-09-05 17:02 ` [PATCH 1/4] tools: hv: Fix file handle leak K. Y. Srinivasan
2012-09-05 17:02   ` [PATCH 2/4] tools: hv: Fix exit() error code K. Y. Srinivasan
2012-09-05 17:02   ` [PATCH 3/4] tools: hv: Check for read/write errors K. Y. Srinivasan
2012-09-05 17:02   ` [PATCH 4/4] tools: hv: Parse /etc/os-release K. Y. Srinivasan
2012-09-05 16:58     ` Alan Cox
2012-09-05 18:16       ` KY Srinivasan
2012-09-05 19:11 ` [PATCH 0/4] Tools: hv Greg KH
2012-09-05 19:24   ` KY Srinivasan
2012-09-05 19:38     ` Greg KH [this message]
2012-09-05 19:49       ` KY Srinivasan

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=20120905193852.GA412@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=apw@canonical.com \
    --cc=ben@decadent.org.uk \
    --cc=dcbw@redhat.com \
    --cc=devel@linuxdriverproject.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=thozza@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox