This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: ChangeLogs in commit messages
- From: Gary Benson <gbenson at redhat dot com>
- To: Andreas Schwab <schwab at linux-m68k dot org>
- Cc: Sergio Durigan Junior <sergiodj at redhat dot com>, 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, 4 Sep 2014 10:06:16 +0100
- 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>
Andreas Schwab wrote:
> Sergio Durigan Junior <sergiodj@redhat.com> writes:
> > Siva Chandra kindly pointed to me that gitweb manages to figure
> > out the actual push date. So I did a little more research on
> > git-log's manpage, and saw that there is a "--pretty=fuller"
> > option which shows the push date.
>
> 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.
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.
Cheers,
Gary
--
http://gbenson.net/