public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Avi Kivity <avi@qumranet.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Carsten Otte <cotte@de.ibm.com>
Subject: Re: small author mixup  (was: git pull KVM updates for 2.6.26rc)
Date: Wed, 30 Apr 2008 10:20:32 +0200	[thread overview]
Message-ID: <20080430082032.GA23528@elte.hu> (raw)
In-Reply-To: <200804301012.05179.borntraeger@de.ibm.com>


* Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> While it is not a typical case, is there a better way of specifying 
> multiple authors to avoid future confusion?

i think the established rule is that there's one Author field per 
commit. Multiple authors should either submit a tree with multiple 
commits (which shows the exact lineage of work) - or, for nontrivial 
joint work where the development tree would be way too messy, expose 
proper credits in copyrights/credit info in the source code. It's seldom 
that work is split exactly in half - better spell out who did what both 
in the source code and in the commit log - without trying to formalize 
the From/Author line. [which line will always be imprecise for multiple 
authors.]

	Ingo

  reply	other threads:[~2008-04-30  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 15:39 [GIT PULL] KVM updates for 2.6.26rc Avi Kivity
2008-04-30  8:12 ` small author mixup (was: git pull KVM updates for 2.6.26rc) Christian Borntraeger
2008-04-30  8:20   ` Ingo Molnar [this message]
2008-04-30  8:36   ` small author mixup Avi Kivity

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=20080430082032.GA23528@elte.hu \
    --to=mingo@elte.hu \
    --cc=avi@qumranet.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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