From: Junio C Hamano <gitster@pobox.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: git reflog --date
Date: Tue, 21 Oct 2014 11:06:47 -0700 [thread overview]
Message-ID: <xmqq8uk91emg.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAHQ6N+rb6eNC0_uzCAdH-HNb_SmdG4-W9DgmVKjfNpRcKKxk=w@mail.gmail.com> (John Tapsell's message of "Tue, 21 Oct 2014 18:31:42 +0100")
John Tapsell <johnflux@gmail.com> writes:
> For me, writing "git reflog @{now}" is a lot less intuitive than "git
> reflog --date"
>
> Currently the top google search for this question is here:
>
> http://stackoverflow.com/questions/17369254/is-there-a-way-to-cause-git-reflog-to-show-a-date-alongside-each-entry
>
> Which doesn't mention "@{now}" at all.
I would say that a site where cluelesses attempt to lead other
cluelesses is not the best source of information ;-), but that tells
us that either our docs are not read by people or they do not give
necessary information to them clearly enough.
> My opinion:
>
> 1. Add --date as an option to reflog. Perhaps using the log.date
> format as the default.
> 2. Document --date in the man page for "git reflog"
> 3. Document @{now} in the man page for "git reflog"
>
> Sound good?
The order of changes is questionable, but other than that, I think
that would be a good way forward.
next prev parent reply other threads:[~2014-10-21 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:11 git reflog --date John Tapsell
2014-10-21 17:24 ` Junio C Hamano
2014-10-21 17:31 ` John Tapsell
2014-10-21 18:06 ` Junio C Hamano [this message]
2014-10-21 18:12 ` John Tapsell
2014-10-21 23:11 ` Junio C Hamano
2014-10-21 22:21 ` Junio C Hamano
2014-11-04 17:06 ` Phil Hord
-- strict thread matches above, loose matches on Subject: below --
2020-08-12 0:28 Craig H Maynard
2020-08-12 9:14 ` Jeff King
2020-08-12 12:34 ` Craig H Maynard
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8uk91emg.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).