Re: Recording the date at which a change was pushed to Savannah

[Glenn Morris <rgm@gnu.org>]

So what I take away from this is what I can't know when Y happened, I
can only know it was after X and before Z. Whoop.

I find the Git date fields actively misleading, especially in the case
of commits merged from another branch. Eg on master:

git log -1 --format=fuller 2fa082c00315801f0215685aa6032179615d2b55 

  AuthorDate: Wed Nov 19 20:33:17 2014 +0200
  CommitDate: Wed Nov 19 20:35:17 2014 +0200

This change was actually pushed to trunk 10 days later, on Nov 29.

Obviously the same sort of thing will apply if someone delays pushing
their local commits to Savannah. Or the next time a long-lived feature
branch gets merged to master.

I've already been confused by this once (in trying to figure out what
went on in some recent merge commits), and expect to be confused by it
again in future. Basically all I can do is ignore the Date fields
completely, or treat them as lower limits.