This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: ChangeLogs in commit messages
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Gary Benson <gbenson at redhat dot com>
- Cc: Andreas Schwab <schwab at linux-m68k dot org>, Joel Brobecker <brobecker at adacore dot com>, gdb at sourceware dot org, Andreas Arnez <arnez at linux dot vnet dot ibm dot com>, Doug Evans <dje at google dot com>
- Date: Thu, 04 Sep 2014 10:22:41 -0400
- Subject: Re: ChangeLogs in commit messages
- Authentication-results: sourceware.org; auth=none
- References: <20140814083231 dot GA6283 at blade dot nx> <20140814125224 dot GF4924 at adacore dot com> <8761h4fmu4 dot fsf at redhat dot com> <87mwage6x2 dot fsf at redhat dot com> <871trsuz55 dot fsf at igel dot home> <20140904090616 dot GA23758 at blade dot nx>
On Thursday, September 04 2014, Gary Benson wrote:
>> There is no such thing as a "push date". What you see is the author
>> date and the committer date. But both are set during the local
>> commit, and are unrelated to the point of time of pushing the
>> commits to the remote repository.
>
> Yeah, in git no file (object) is modified when you push or pull
> commits, they're just copied from one place to another.
Yeah, sorry for not being fluent in git's parlance.
> The committer date on the commit you mentioned is likely the time
> I updated the ChangeLog prior to pushing, so that date will be the
> "push date", but that's not guaranteed to be the case for all
> commits.
Right. Anyway, I still consider it is valid to include this info
(author and date) in the commit message.
Thanks,
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/