Re: What should "git submodule summary" give before an initial commit?

Heya,

On Thu, Mar 4, 2010 at 07:43, Junio C Hamano [off-list ref] wrote:

I doubt it would be very much useful as a general feature, as sometimes we
default to HEAD because we want a tree-ish (in which case using "empty
tree" would be appropriate) and other times because we want an actual
commit (e.g. "git commit --amend" should exit, not "amend an empty tree")
and we would need to be careful to study each codepath and use the
appropriate one.

Yes, I think if we add such a "default to HEAD or empty tree" option
to parse_opt we shouldn't just plug it in anywhere we default to HEAD.

But you are welcome to try and prove me wrong with a working patch ;-).

Ah, I was hoping perhaps one of our still-in-hiding prospective gsoc
students might feel up to the task, I am short on free time lately (I
barely have enough time for Melange), the little git time I do have is
spent on adding write support to git-remote-hg. So! To all you people
that want to be a gsoc student for git, now's your "opportune moment"
to impress us ;).

-- 
Cheers,

Sverre Rabbelier