git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Pretty-print date in 'git log'

From
Petr Baudis <pasky@ucw.cz>
Date
Apr 18, 2005, 10:27 UTC
Message-ID
<20050418102744.GK1461@pasky.ji.cz>
In-Reply-To
<1113808105.5286.1.camel@localhost.localdomain>

Dear diary, on Mon, Apr 18, 2005 at 09:08:24AM CEST, I got a letter where David Woodhouse <dwmw2@infradead.org> told me that...

Show 6 quoted lines
> On Mon, 2005-04-18 at 07:43 +0100, Sanjoy Mahajan wrote:
> > Is this short script good enough:
> 
> It's not far off; thanks. We might as well just do it like that inside
> gitlog.sh. Could do with falling back to just printing the input if it
> can't parse it -- the git repo has old-style dates in it still.
Yes. As far as I'm concerned, I'd put such stuff to git log, and extend
it usage so that it is possible to print individual log entries with it
- just make it accept a _range_ of commits, and then do
	git log $commit $commit
And maybe options for changelog-suitable output (RMK-like) etc.
-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
Next: David Woodhouse
Message 1 of 2 in “Re: [PATCH] Pretty-print date in 'git log'”
  1. Petr BaudisApr 18, 2005
  2. David WoodhouseApr 18, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.