Thread (19 messages) 19 messages, 4 authors, 2016-06-15

Re: several date related issues

flat view

From: H.Merijn Brand <hidden>
Date: 2016-06-15 23:05:31

On Thu, 25 Jun 2015 08:44:45 -0400, Jeff King [off-list ref] wrote:
On Thu, Jun 25, 2015 at 01:19:01PM +0200, H.Merijn Brand wrote:
quoted
*** Dates do not respect LC_TIME
Right, we use our own routines for formatting the dates, and not
strftime. And it probably should stay that way in general, as git's
output is often meant to be parsed.

That being said, I do not think it would be wrong to have a date-mode
that just showed strftime("%c"), or some other arbitrary strftime
string.  You could then set log.date as appropriate for human
consumption.
Yes please :)

 --date=lc
 --date=lc_time
 --date=locale

all spring to mind as valid options
quoted
*** git log --date-order and --author-date-order do not order by date
Correct. The documentation says:

   --date-order
     Show no parents before all of its children are shown, but otherwise
     show commits in the commit timestamp order.

In your example, one commit is the parent of the other, so it hits the
first part of the sentence, and the dates are never even compared.
That is what I gathered, and concluded that the option name is
misleading
There is not a simple way to show commits in arbitrary order without
respect to parentage. I think you'd have to do something like:

  git log --format='%at %H' |
  sort -rn |
  cut -d' ' -f2 |
  git log --stdin --no-walk
I'd like that as gitk option!

-- 
H.Merijn Brand  http://tux.nl   Perl Monger  http://amsterdam.pm.org/
using perl5.00307 .. 5.21   porting perl5 on HP-UX, AIX, and openSUSE
http://mirrors.develooper.com/hpux/        http://www.test-smoke.org/
http://qa.perl.org   http://www.goldmark.org/jeff/stupid-disclaimers/

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help