From: Zabre <427@free.fr>
To: git@vger.kernel.org
Subject: Re: Force commit date
Date: Thu, 29 Jan 2009 11:48:57 -0800 (PST) [thread overview]
Message-ID: <1233258537869-2240926.post@n2.nabble.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0901291406000.19665@iabervon.org>
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.
next prev parent reply other threads:[~2009-01-29 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 18:30 Force commit date Zabre
2009-01-29 18:37 ` Sverre Rabbelier
2009-01-29 18:47 ` Zabre
2009-01-29 18:45 ` Zabre
2009-01-29 18:55 ` Markus Heidelberg
2009-01-29 19:02 ` Zabre
2009-01-29 19:10 ` Daniel Barkalow
2009-01-29 19:48 ` Zabre [this message]
2009-01-29 20:06 ` Zabre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1233258537869-2240926.post@n2.nabble.com \
--to=427@free.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).