From: "Francis Moreau" <francis.moro@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org, "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: Remote git-describe ?
Date: Wed, 24 Jan 2007 13:50:56 +0100 [thread overview]
Message-ID: <38b2ab8a0701240450s614df3bevf95e62add1b1783f@mail.gmail.com> (raw)
In-Reply-To: <7vps94fweq.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> "Francis Moreau" <francis.moro@gmail.com> writes:
>
>> ... 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?
>
yes. see below...
> 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.
>
I agree in the context I gave, it's useless.
>
> 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.
>
Actually I'd like to generate an archive from a git server. And
I want to give the name of the archive file, the ouptut given by
'git describe'.
Since I can pass --remote to 'git archive', I do not need anymore
to clone the repo before generating the archive. But I still needs
it only to run 'git describe' thus my question...
thanks
--
Francis
prev parent reply other threads:[~2007-01-24 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 10:31 Remote git-describe ? Francis Moreau
2007-01-24 11:03 ` Johannes Schindelin
2007-01-24 11:13 ` Francis Moreau
2007-01-24 11:29 ` Johannes Schindelin
2007-01-24 12:21 ` Junio C Hamano
2007-01-24 12:34 ` Junio C Hamano
2007-01-24 13:01 ` Santi Béjar
2007-01-24 13:57 ` Johannes Schindelin
2007-01-24 14:28 ` Simon 'corecode' Schubert
2007-01-24 15:23 ` Nicolas Pitre
2007-01-24 12:50 ` Francis Moreau [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38b2ab8a0701240450s614df3bevf95e62add1b1783f@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).