# git merge --date --author 5 messages from 2014-03-07 to 2014-03-10. Participants: Yann Droneaud, Michael Haggerty, Andreas Schwab, Junio C Hamano. Thread: https://gitlist.dev/t/36097 ## Yann Droneaud, 2014-03-07 10:30 Subject: git merge --date --author Message-ID: <1394188215.3257.17.camel@localhost.localdomain> URL: https://gitlist.dev/e/1394188215.3257.17.camel%40localhost.localdomain ``` Hi, I was trying to rebuild some history and found myself trying to use some options with git merge which are available in git commit: git merge \ --date "2013-12-31 23:59:59 +0000" \ --author "Happy New Year " \ current-year But unfortunately, unlike git commit, git merge doesn't support either --date or --author. I can work around with environment variables: GIT_AUTHOR_DATE="2013-12-31 23:59:59 +0000" \ GIT_AUTHOR_NAME="Happy New Year" \ GIT_AUTHOR_EMAIL="happy.new-year@gregorian.calendar" \ git merge current-year But I'd like to know if there's a specific reason for git merge to not support --date and --author ? Regards. -- Yann Droneaud OPTEYA ``` ## Michael Haggerty, 2014-03-07 11:41 Subject: Re: git merge --date --author Message-ID: <5319B04D.6080906@alum.mit.edu> URL: https://gitlist.dev/e/5319B04D.6080906%40alum.mit.edu In-Reply-To: <1394188215.3257.17.camel@localhost.localdomain> ``` On 03/07/2014 11:30 AM, Yann Droneaud wrote: > I was trying to rebuild some history and found myself trying to use some > options with git merge which are available in git commit: > > git merge \ > --date "2013-12-31 23:59:59 +0000" \ > --author "Happy New Year " \ > current-year > > But unfortunately, unlike git commit, git merge doesn't support either > --date or --author. > > I can work around with environment variables: > > GIT_AUTHOR_DATE="2013-12-31 23:59:59 +0000" \ > GIT_AUTHOR_NAME="Happy New Year" \ > GIT_AUTHOR_EMAIL="happy.new-year@gregorian.calendar" \ > git merge current-year You can also use git merge --no-commit [...] git commit --date ... --author ... > But I'd like to know if there's a specific reason for git merge to not > support --date and --author ? None that I can think of, except that nobody has implemented it. Don't forget that the merge invocation might not lead immediately to a commit (if there is a conflict, or if --no-commit is used) so the metadata that is passed to its command line would have to be tucked away safely somewhere until the merge commit is finally ready to be created. Michael -- Michael Haggerty mhagger@alum.mit.edu http://softwareswirl.blogspot.com/ ``` ## Andreas Schwab, 2014-03-07 12:58 Subject: Re: git merge --date --author Message-ID: <87y50mxj0b.fsf@igel.home> URL: https://gitlist.dev/e/87y50mxj0b.fsf%40igel.home In-Reply-To: <1394188215.3257.17.camel@localhost.localdomain> ``` Yann Droneaud writes: > But I'd like to know if there's a specific reason for git merge to not > support --date and --author ? It's rather unusual that a merge is performed on behalf of a different author. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ``` ## Junio C Hamano, 2014-03-07 19:43 Subject: Re: git merge --date --author Message-ID: URL: https://gitlist.dev/e/xmqqvbvpu757.fsf%40gitster.dls.corp.google.com In-Reply-To: <87y50mxj0b.fsf@igel.home> ``` Andreas Schwab writes: > Yann Droneaud writes: > >> But I'd like to know if there's a specific reason for git merge to not >> support --date and --author ? > > It's rather unusual that a merge is performed on behalf of a different > author. Yes. Michael's "Nobody bothered to implement it" is also correct but the reason why nobody bothered to most likely is due to "why would you want to lie?". If the use case is to rebuild history, you would need to be able to also lie about the committer, so >> git merge \ >> --date "2013-12-31 23:59:59 +0000" \ >> --author "Happy New Year " \ >> current-year in such a history-rebuild script would not be sufficient. The script can set necessary environment variables to lie about both author and commiter, though, of course. ``` ## Yann Droneaud, 2014-03-10 12:52 Subject: Re: git merge --date --author Message-ID: <1394455972.3257.51.camel@localhost.localdomain> URL: https://gitlist.dev/e/1394455972.3257.51.camel%40localhost.localdomain In-Reply-To: ``` Hi, Le vendredi 07 mars 2014 à 11:43 -0800, Junio C Hamano a écrit : > Andreas Schwab writes: > > > Yann Droneaud writes: > > > >> But I'd like to know if there's a specific reason for git merge to not > >> support --date and --author ? > > > > It's rather unusual that a merge is performed on behalf of a different > > author. > > Yes. Michael's "Nobody bothered to implement it" is also correct > but the reason why nobody bothered to most likely is due to "why > would you want to lie?". > When was Git changed in some kind of TSA agent one has to bribe to get allowed to cross^Wcommit ? Why git lawyer is not implemented ? I want a fair trial ! And before adding to Git a perfect lie detector (how will it able to make the difference between truth and lie ? then, will it be able to make the difference between good and bad ?, oh god, no !), I would prefer to have it detect bugs before one could commit instead. You seems to think I'm lying, but I'm not a liar: I just need to make some arrangements with the history under another identity, as I could be legally bound to. So it may sound like a lie for you, but ultimately, it's the plain truth. So as the tool is not in position to distinguish lie from truth, I'd prefer to not see this concept brought here. > If the use case is to rebuild history, you would need to be able to > also lie about the committer, so > > >> git merge \ > >> --date "2013-12-31 23:59:59 +0000" \ > >> --author "Happy New Year " \ > >> current-year > > in such a history-rebuild script would not be sufficient. The > script can set necessary environment variables to lie about both > author and commiter, though, of course. > Thanks for reminding this: I have to use GIT_COMMITER_DATE, GIT_COMMITER_NAME and GIT_COMMITER_EMAIL. As I'm not calling for adding --date and --author, I will continue to use the environment variables: they're good enough for the job. Regards. -- Yann Droneaud OPTEYA ```