From: Johannes Sixt <johannes.sixt@telecom.at>
To: git@vger.kernel.org
Subject: Re: cg-clone not fetching all tags?
Date: Sat, 29 Apr 2006 23:42:16 +0200 [thread overview]
Message-ID: <200604292342.16306.johannes.sixt@telecom.at> (raw)
In-Reply-To: <20060429170542.GJ27689@pasky.or.cz>
On Saturday 29 April 2006 19:05, Petr Baudis wrote:
> Hi,
>
> Dear diary, on Sat, Apr 29, 2006 at 04:00:42PM CEST, I got a letter
> where Wolfgang Denk <wd@denx.de> said that...
>
> > it seems that "cg-clone" does not fetch all tags any more - only the
> > most recent ones (modiufied in the last N days?) seem to be fetched?
> > [Eventually the "N days" might correspond to "changing tools to
> > version X", but I have no way to find out.]
> >
> > This happens only when using HTTP; using ssh or rsync works fine.
> > Also, if we follow the "cg-clone" by a "git-fetch -t" command, this
> > will load the missing tags.
> >
> > Is this intentional, or am I doing anything wrong?
> >
> > [For testing, try "cg-clone http://www.denx.de/git/u-boot.git"]
>
> you need to run git-update-server-info every time you add or update a
> tag (or best every time you push). See the NOTES section of
> cg-admin-setuprepo documentation for details on how to set it up to be
> called automagically at every push.
There are two types of tags: They can point to
1. a commit object
2. a proper tag object (which in turn references the commit)
git-update-server-info seems to generate info only for case 2, and so are the
only ones that http can fetch.
-- Hannes
next prev parent reply other threads:[~2006-04-29 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 10:52 cg-clone not fetching all tags? Wolfgang Denk
2006-04-29 14:00 ` Wolfgang Denk
2006-04-29 17:05 ` Petr Baudis
2006-04-29 21:42 ` Johannes Sixt [this message]
2006-04-29 22:11 ` Wolfgang Denk
2006-04-29 22:54 ` Johannes Sixt
2006-04-30 4:11 ` Junio C Hamano
2006-04-30 13:48 ` Wolfgang Denk
2006-04-29 22:11 ` Wolfgang Denk
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=200604292342.16306.johannes.sixt@telecom.at \
--to=johannes.sixt@telecom.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.