Re: Remote git-describe ?

From: Junio C Hamano <junkio@cox.net>
Date: Jan 24, 2007, 12:21 UTC
Message-ID: <7vps94fweq.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <38b2ab8a0701240313w64c2df57w2542b63eba2294e0@mail.gmail.com>

"Francis Moreau" <francis.moro@gmail.com> writes:

Show 7 quoted lines

> ... Givinig that I would use it to describe the HEAD of the kernel repo:
>
>        $ git describe --remote=<git-server> HEAD
>
> this would make the server parse all commits between HEAD and the
> closest tag which seems to me a lot cheaper than downloading the whole
> repo...

Do you mean you want to have the server describe the HEAD the server side has (not the HEAD in your repository)? Why?

I suspect the real motivation of your question lies elsewhere and not in "describe".

Suppose we had such a service on the server side, and you asked the server twice and got these (at different times, of course):

	v2.6.20-rc5-g419dd83
	v2.6.20-rc5-gde14569

What useful information can you get between the two?

Nothing.

The commit object names are like random numbers and 419dd83 may or may not be older than de14569. The "hash" part of the output is meaningless for you until you actually have the history to poke at with "git log", "git diff" and friends.

Another request might give you this:

	v2.6.20-rc6

At least, between this one and the previous two, you have a little bit of information that you can use: "Ah, another development phase."

So I suspect what you are after is not about using describe remotely or describing where the HEAD is; you want to know if there is a new tag near the tip since the last time you checked.

If that is the case, "git-ls-remote --tags" is probably what you want.