git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Francis Moreau" <francis.moro@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Remote git-describe ?
Date: Wed, 24 Jan 2007 12:13:17 +0100	[thread overview]
Message-ID: <38b2ab8a0701240313w64c2df57w2542b63eba2294e0@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701241201410.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On 1/24/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Wed, 24 Jan 2007, Francis Moreau wrote:
>
> > I'm looking for a command that would give the same output than 'git
> > describe' but on a remote server.
> >
> > Is this possible ?
>
> It would be possible; at a high cost (especially on the remote server):
> You definitely need _all_ commits between the commit you want to describe
> and the tag it eventually finds, and possibly all other commits, too.
>
> So it boils down to fetching all commit objects. It is much cheaper, and
> more efficient, to just fetch the repo and do it locally.
>

really ? 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...
-- 
Francis

  reply	other threads:[~2007-01-24 11:13 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 [this message]
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

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=38b2ab8a0701240313w64c2df57w2542b63eba2294e0@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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).