[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: git reflog --date
From:       John Tapsell <johnflux () gmail ! com>
Date:       2014-10-21 18:12:04
Message-ID: CAHQ6N+qkQbmhY-nueF28+iRhbVvH__gihXb6yyj3dRbgpbV18g () mail ! gmail ! com
[Download RAW message or body]

Great - now I just need to persuade someone very nice nicely.. :-)

On 21 October 2014 19:06, Junio C Hamano <gitster@pobox.com> wrote:
> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[prev in list] [next in list] [prev in thread] [next in thread]