Dear diary, on Mon, Apr 11, 2005 at 01:46:50AM CEST, I got a letter where Linus Torvalds <[EMAIL PROTECTED]> told me that... > > > On Mon, 11 Apr 2005, Petr Baudis wrote: > > > > (BTW, it would be useful to have a tool which just blindly takes what > > you give it on input and throws it to an object of given type; I will > > need to construct arbitrary commits during the rebuild if I'm to keep > > the correct dates.) > > Hah. That's what "COMMITTER_NAME" "COMMITTER_EMAIL" and "COMMITTER_DATE" > are there for. > > There's two things to commits: when (and by whom) it was committed to a > tree, and when the changes were really done. > > So set the COMMITTER_xxx things to the person/time you want to consider > the _original_ one, and let "commit-tree" author you as the creator of the > commit itself. The regular "ChangeLog" thing should only show the author > and original time, but it's nice to see who created the commit itself.
I already use those - look at my ChangeLog. (That's because for certain reasons I'm working on git in a half-broken chrooted environment.) When rebuilding the tree from scratch, I wanted like to do it transparently - that is, so that noone could notice that I rebuilt it, since it effectively still _is_ the original tree from the data standpoint, just the history flow is actually correct this time. > Btw, the "COMMITTER_xxxx" environment variables are very confusingly > named. They actually go into the _author_ line in the commit object. I'm a > total retard, and I really don't know why I called it "COMMITTER_xxx" > instead of "AUTHOR_xxx". So, who will fix it in his tree first! ;-) -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ 98% of the time I am right. Why worry about the other 3%. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/