{"thread":{"id":"13331","subject":"Re: small author mixup","startedAt":"2008-04-30T08:36:15Z","lastAt":"2008-04-30T08:36:15Z","messageCount":1,"participants":["Avi Kivity"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"75653","messageId":"48182F7F.9000400@qumranet.com","threadId":"13331","inReplyTo":"200804301012.05179.borntraeger@de.ibm.com","subject":"Re: small author mixup","fromName":"Avi Kivity","fromEmail":"avi@qumranet.com","sentAt":"2008-04-30T08:36:15Z","receivedAt":"2008-04-30T08:36:15Z","isPatch":false,"sender":{"key":"avi@qumranet.com","avatar":null},"body":"Christian Borntraeger wrote:\n> Am Sonntag, 27. April 2008 schrieb Avi Kivity:\n>   \n>> Carsten Otte (4):\n>>       s390: KVM preparation: provide hook to enable pgstes in user pagetable\n>>       KVM: s390: interrupt subsystem, cpu timer, waitpsw\n>>       KVM: s390: API documentation\n>>       s390: KVM guest: detect when running on kvm\n>>\n>> Christian Borntraeger (10):\n>>       KVM: kvm.h: __user requires compiler.h\n>>       s390: KVM preparation: host memory management changes for s390 kvm\n>>       s390: KVM preparation: address of the 64bit extint parm in lowcore\n>>       KVM: s390: sie intercept handling\n>>       KVM: s390: intercepts for privileged instructions\n>>       KVM: s390: interprocessor communication via sigp\n>>       KVM: s390: intercepts for diagnose instructions\n>>       KVM: s390: add kvm to kconfig on s390\n>>       KVM: s390: update maintainers\n>>       s390: KVM guest: virtio device support, and kvm hypercalls\n>>     \n>\n> Thats interesting, some of these patches should actually be credited to \n> Carsten - and in fact on kvm.git master they are credited to Carsten.\n>\n> I think the problem is, that these patches contained multiple From lines. On \n> kvm.git the first line (Carsten) was used. When you transferred these patches \n> to the kvm.git-2.6.26-branch, git used the next From-line as the original one \n> was already removed.\n>\n> While it is not a typical case, is there a better way of specifying multiple \n> authors to avoid future confusion?\n\nIt's probably due to my heavy use of git cherry-pick, rebase, and rebase \n-i.  I couldn't reproduce this with a test that mimics that workflow, so \neither it has been fixed already, or it's a little more subtle.\n\nI don't think you should change anything to avoid this.  I'll keep an \neye open for this, and if it happens again I'll fix it locally and send \na proper bug report to the git mailing list.\n\n-- \nAny sufficiently difficult bug is indistinguishable from a feature.\n"}]}