Hi Stephen I noticed something currious today in linux-next. There are, what looks to me like, duplicate patches with different commit id's but identical contents. Perhaps this is just a git artefact that I don't know about, but it seemed currious enough that I thought I'd ask. The two patches are these (from 'git log'): commit a9c3809db31be860db4e8ecf8ab359159c935a3b Author: Jesper Juhl <jj@xxxxxxxxxxxxx> Date: Wed Feb 23 23:45:55 2011 +0100 commit 4b2f67d756cf4a5ed8e8d11caa7dcea06c41a09e Author: Jesper Juhl <jj@xxxxxxxxxxxxx> Date: Wed Feb 23 23:45:55 2011 +0100 They are completely identical except for the commit id. If I do a 'git log drivers/regulator/mc13xxx-regulator-core.c' I only see commit 4b2f67d756cf4a5ed8e8d11caa7dcea06c41a09e . Please enlighten me if this is perfectly normal and not a problem. Currently I'm a bit puzzled by two commit id's showing up for the same change.. -- Jesper Juhl <jj@xxxxxxxxxxxxx> http://www.chaosbits.net/ Plain text mails only, please. Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
