Daniel Barkalow wrote: > > You may want to consider whether those dates make most sense as the date > of the commit, or the date the changes were done; git tracks both of > these separately, in part because it's easy to have some work done at one > time, and only make the commit that becomes part of the official project > history much later (and these may be done by different people). > > The date for the changes being done is set with GIT_AUTHOR_DATE > Thank you Daniel, this is very interesting, having a GIT_COMMITTER_DATE and a GIT_AUTHOR_DATE enables me to have both dates, and no need to trick the system then. -- View this message in context: http://n2.nabble.com/Force-commit-date-tp2240539p2240926.html Sent from the git mailing list archive at Nabble.com. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
