Re: Re: Re-done kernel archive - real one?

From: Petr Baudis <pasky@ucw.cz>
Date: Apr 17, 2005, 16:28 UTC
Message-ID: <20050417162829.GK1487@pasky.ji.cz>
In-Reply-To: <20050417162448.A13233@flint.arm.linux.org.uk>

Dear diary, on Sun, Apr 17, 2005 at 05:24:48PM CEST, I got a letter where Russell King <rmk@arm.linux.org.uk> told me that...

Show 5 quoted lines

> However, I've made a start to generate the necessary emails.  How about
> this format?
> 
> I'm not keen on the tree, parent, author and committer objects appearing
> in this - they appear to clutter it up.  What're your thoughts?

I think it would look nicer if you used git log format. Actually...

> #!/bin/sh
> prev=$(cat .git/heads/origin)
> to=$(cat .git/HEAD)

It is preferred to use the commit-id command instead; when git decides to totally dig over its metametadata storage, you won't need to care.

Show 5 quoted lines

> this=$to
> while [ "$this" != "$prev" ]; do
>   cat-file commit $this | sed 's,.*,\t&,'
>   this=$(cat-file commit $this | grep ^parent | cut -d ' ' -f 2)
> done

What about adding support to git log for not caring about side branches (if there are multiple parents, go only over the first one; you might add that as a switch to rev-tree, which would turn it to rev-line ;-)?

Then, you could also easily implement support for passing additional commit ID to git log, and it would then print out the range between these two.

That would do exactly what you want, and would be probably quite usable for other uses too.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor