threads / discuss / 5622

pseudo initial empty commit and tag for git-log and git-describe?

Subject: pseudo initial empty commit and tag for git-log and git-describe?

## tl;dr

4 messages between Sep 20, 2006 and Sep 21, 2006.

replies: 3people: 3as markdown or json

Nguyễn Thái Ngọc Duy· Sep 20, 2006, 13:58 UTC · lore

I'm still uncomfortable with git-log -p unable to show the first commit (git-whatchanged too). Also git-describe refuses to work without any tag. I'm thinking about adding a pseudo empty commit together with a tag so that these commands work. The commit and tag will be created at runtime. They do not actually exist in the object database. I haven't thought about how to implement it yet. Any other ideas?

-- 
Duy
Matthias Kestenholz· Sep 20, 2006, 14:10 UTC · re: Nguyễn Thái Ngọc Duy · lore

Re: pseudo initial empty commit and tag for git-log and git-describe?

hello
On Wed, 2006-09-20 at 20:58 +0700, Nguyễn Thái Ngọc Duy wrote:
Show 7 quoted lines
> I'm still uncomfortable with git-log -p unable to show the first
> commit (git-whatchanged too). Also git-describe refuses to work
> without any tag. I'm thinking about adding a pseudo empty commit
> together with a tag so that these commands work. The commit and tag
> will be created at runtime. They do not actually exist in the object
> database. I haven't thought about how to implement it yet.
> Any other ideas?
you can use git log -p --root  to also display the root commit.
	Matthias
Linus Torvalds· Sep 20, 2006, 15:12 UTC · re: Nguyễn Thái Ngọc Duy · lore

Re: pseudo initial empty commit and tag for git-log and git-describe?

On Wed, 20 Sep 2006, Nguyá»n Thái Ngá»c Duy wrote:
>
> I'm still uncomfortable with git-log -p unable to show the first
> commit (git-whatchanged too).

Both of those work fine with "--root". That option tells git: "I'm interested in the root patch too".

It might make sense to have "--root" be the default, but the problem is that for projects like the Linux kernel where the first commit is a big import, showing it as a patch simply doesn't make sense.

So it would have to be a per-repository decision, depending on whether the repo considers the first commit to be an import or not. Maybe a git-config option?

> Also git-describe refuses to work without any tag.

Now, that's arguably a real bug. You should be able to describe any commit, and if there's no tag that is reachable from it, the "description" should probably just be the SHA1 of the commit.

(Side issue: we should probably also accept the output of "git describe" as a revision name, since it's a bit silly that you can ask git to "describe" a revision, but then git can't actually use the description itself ;)

			Linus

← back to recent threads