Carlos Martín Nieto [off-list ref] writes:
I was surpised when I tried 'git commit --amend --date=now' that git
didn't understand 'now' as a date, which seems like a more obvious
place to fix it.
+1
I really don't think Git wants yet-another-option for each use-case we
find, and accepting "now" as a date (either by hardcoding "now" as an
accepted value, or by running approxidate on the argument of --date).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
On Wed, Dec 21, 2011 at 05:24:57PM +0100, Matthieu Moy wrote:
Carlos Martín Nieto [off-list ref] writes:
quoted
I was surpised when I tried 'git commit --amend --date=now' that git
didn't understand 'now' as a date, which seems like a more obvious
place to fix it.
+1
I really don't think Git wants yet-another-option for each use-case we
find, and accepting "now" as a date (either by hardcoding "now" as an
accepted value, or by running approxidate on the argument of --date).
I'm curious of the use case where one wants "--date=now" but not
"--reset-author". Or is it simply that "--reset-author" is a less
obvious thing to try?
At any rate, if we are going to do that, I agree it should be spelled
"--date=now", and not "--date-now".
-Peff