From: Peter Krefting <peter@softwolves.pp.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFD] use approxidate for "git commit --date=xyz"?
Date: Wed, 7 May 2014 08:22:15 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.00.1405070817580.15517@ds9.cixit.se> (raw)
In-Reply-To: <xmqq1tweec1o.fsf@gitster.dls.corp.google.com>
Junio C Hamano:
> But why does the workflow need --date=now in the first place?
I tend to do this quite a lot, after fixing up a commit using rebase,
I notice that the commit date is when I first started fixing the
issue, even if that was a week or so ago. I then like to reset the
commit date to reflect when I actually was done with it, and try
"commit --amend --date=now".
I just haven't been annoyed enough to patch the code to fix it (so the
git repository at my $dayjob does have a number of commits with the "wrong"
commit time in it [1]), but I would welcome such an addition.
--
\\// Peter - http://www.softwolves.pp.se/
[1] The last such is one that took me about a week to implement:
AuthorDate: 2014-04-15 15:48:38 +0200
CommitDate: 2014-04-22 09:23:25 +0100
it'd look better to have the AuthorDate at the 22nd as well, imho.
prev parent reply other threads:[~2014-05-07 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 21:09 [RFD] use approxidate for "git commit --date=xyz"? Linus Torvalds
2014-04-30 21:34 ` Junio C Hamano
2014-05-01 22:06 ` Jeff King
2014-05-02 1:03 ` [PATCH 0/4] approxidate for "git commit --date=foo" Jeff King
2014-05-02 1:06 ` [PATCH 1/4] commit: use split_ident_line to compare author/committer Jeff King
2014-05-02 1:07 ` [PATCH 2/4] pretty: make show_ident_date public Jeff King
2014-05-02 1:10 ` [PATCH 3/4] commit: print "Date" line when the user has set date Jeff King
2014-05-02 1:12 ` [PATCH 4/4] commit: accept more date formats for "--date" Jeff King
2014-05-07 7:22 ` Peter Krefting [this message]
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=alpine.DEB.2.00.1405070817580.15517@ds9.cixit.se \
--to=peter@softwolves.pp.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.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).