From: Junio C Hamano <junkio@cox.net>
To: Wolfgang Denk <wd@denx.de>
Cc: git@vger.kernel.org, pasky@suse.cz
Subject: Re: cg-clone not fetching all tags?
Date: Sat, 29 Apr 2006 21:11:07 -0700 [thread overview]
Message-ID: <7vaca31z50.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060429221114.557FC35288F@atlas.denx.de> (Wolfgang Denk's message of "Sun, 30 Apr 2006 00:11:14 +0200")
Wolfgang Denk <wd@denx.de> writes:
> In message <200604292342.16306.johannes.sixt@telecom.at> you wrote:
>>
>> 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.
>
> And git-cvsimport (at least older versions of it) imports CVS tags
> only as type 1 ?
>
> That would perfectly explain the situation. How can this be fixed?
I suspect there is no need to manufacture the tag. Something
like this should do.
*WARNING* Since I do not do Porcelain, and I am not a Cogito
user, this is obviously untested. In addition, I am seriously
drunk right now...
-- >8 --
[PATCH] (cogito) Auto-follow lightweight tags as well.
---
diff --git a/cg-fetch b/cg-fetch
index 687e6b9..39764c7 100755
--- a/cg-fetch
+++ b/cg-fetch
@@ -218,7 +218,8 @@ fetch_tags()
git-ls-remote --tags "$uri" |
# SHA1 refs/tags/v0.99.8^{} --> SHA1 tags/v0.99.8
# where SHA1 is the object v0.99.8 tag points at.
- sed -ne 's:\([^ ]\) refs/\(tags/.*\)^{}$:\1 \2:p' |
+ sed -n -e 's:\([^ ]\) refs/\(tags/.*\)^{}$:\1 \2:p' \
+ -e 's:\([^ ]\) refs/\(tags/.*\)$:\1 \2:p|' \
while read sha1 tagname; do
# Do we have the tag itself?
[ -s "$_git/refs/$tagname" ] && continue
next prev parent reply other threads:[~2006-04-30 4:11 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
2006-04-29 22:11 ` Wolfgang Denk
2006-04-29 22:54 ` Johannes Sixt
2006-04-30 4:11 ` Junio C Hamano [this message]
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=7vaca31z50.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=wd@denx.de \
/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.