From: Avi Kivity <avi@qumranet.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Carsten Otte <cotte@de.ibm.com>,
git@vger.kernel.org
Subject: Re: small author mixup
Date: Wed, 30 Apr 2008 11:36:15 +0300 [thread overview]
Message-ID: <48182F7F.9000400@qumranet.com> (raw)
In-Reply-To: <200804301012.05179.borntraeger@de.ibm.com>
Christian Borntraeger wrote:
> Am Sonntag, 27. April 2008 schrieb Avi Kivity:
>
>> Carsten Otte (4):
>> s390: KVM preparation: provide hook to enable pgstes in user pagetable
>> KVM: s390: interrupt subsystem, cpu timer, waitpsw
>> KVM: s390: API documentation
>> s390: KVM guest: detect when running on kvm
>>
>> Christian Borntraeger (10):
>> KVM: kvm.h: __user requires compiler.h
>> s390: KVM preparation: host memory management changes for s390 kvm
>> s390: KVM preparation: address of the 64bit extint parm in lowcore
>> KVM: s390: sie intercept handling
>> KVM: s390: intercepts for privileged instructions
>> KVM: s390: interprocessor communication via sigp
>> KVM: s390: intercepts for diagnose instructions
>> KVM: s390: add kvm to kconfig on s390
>> KVM: s390: update maintainers
>> s390: KVM guest: virtio device support, and kvm hypercalls
>>
>
> Thats interesting, some of these patches should actually be credited to
> Carsten - and in fact on kvm.git master they are credited to Carsten.
>
> I think the problem is, that these patches contained multiple From lines. On
> kvm.git the first line (Carsten) was used. When you transferred these patches
> to the kvm.git-2.6.26-branch, git used the next From-line as the original one
> was already removed.
>
> While it is not a typical case, is there a better way of specifying multiple
> authors to avoid future confusion?
It's probably due to my heavy use of git cherry-pick, rebase, and rebase
-i. I couldn't reproduce this with a test that mimics that workflow, so
either it has been fixed already, or it's a little more subtle.
I don't think you should change anything to avoid this. I'll keep an
eye open for this, and if it happens again I'll fix it locally and send
a proper bug report to the git mailing list.
--
Any sufficiently difficult bug is indistinguishable from a feature.
prev parent reply other threads:[~2008-04-30 8:36 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
2008-04-30 8:36 ` Avi Kivity [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=48182F7F.9000400@qumranet.com \
--to=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=git@vger.kernel.org \
--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