git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Force commit date

From
ZZabre <427@free.fr>
Date
Jan 29, 2009, 19:48 UTC
Message-ID
<1233258537869-2240926.post@n2.nabble.com>
In-Reply-To
<alpine.LNX.1.00.0901291406000.19665@iabervon.org>
Daniel Barkalow wrote:
Show 9 quoted lines
> 
> 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.
Previous: Daniel BarkalowNext: Zabre
Message 8 of 9 in “Force commit date”
  1. ZabreJan 29, 2009
  2. Sverre RabbelierJan 29, 2009
  3. ZabreJan 29, 2009
  4. ZabreJan 29, 2009
  5. Markus HeidelbergJan 29, 2009
  6. ZabreJan 29, 2009
  7. Daniel BarkalowJan 29, 2009
  8. ZabreJan 29, 2009
  9. ZabreJan 29, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.