From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Git Mailing List <git@vger.kernel.org>
Subject: Q about the date format in "git commit --date=..." and such
Date: Sun, 06 Mar 2011 17:07:52 +0100 [thread overview]
Message-ID: <4D73B158.5040409@dirk.my1.cc> (raw)
Hello,
I frequently change a file in my repo and commit it with
"git commit -a -C deadbeef", i.e. using an older commit message. The
"-C" switch also re-uses the author timestamp of the given SHA1, which
is not what I want. So I tried the "--date=..." switch in addition,
which works fine.
Instead of giving an exact timestamp (like "--date='06.03.2011 16:50'")
I'd prefer to just say "--date=now". Is that somehow possible? If not:
would the community appreciate it, if I would try to implement this?
I imagine to translate "now" to "localtime(time(0))". Would that be good?
Dirk
next reply other threads:[~2011-03-06 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 16:07 Dirk Süsserott [this message]
2011-03-07 16:54 ` Q about the date format in "git commit --date=..." and such Jeff King
2011-03-08 0:20 ` Junio C Hamano
2011-03-08 1:16 ` Jeff King
2011-03-08 18:51 ` Andreas Schwab
2011-03-08 19:20 ` Dirk Süsserott
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=4D73B158.5040409@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--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).