All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gerald (Jerry) Carter" <jerry@samba.org>
To: git@vger.kernel.org
Subject: Re: Missing tags from git-clone, but not git-clone -l ?
Date: Sun, 07 Oct 2007 13:58:55 -0500	[thread overview]
Message-ID: <47092C6F.7070108@samba.org> (raw)
In-Reply-To: <4709242F.7070004@samba.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gerald (Jerry) Carter wrote:

> I'm really a but stumped on this one.  I've got a set of tags
> (created by git-svnimport):
> 
>   $ git tag -l release-4*
>   release-4-0-0tp1
>   release-4-0-0tp2
>   release-4-0-0tp3
>   release-4-0-0tp4
> 
> but when I "git-clone samba-svnimport tags-test"", one tag
> is missing.
> 
>   $ git tag -l release-4*
>   release-4-0-0tp2
>   release-4-0-0tp3
>   release-4-0-0tp4
> 
> Running git-clone -l works as expected (i.e. the tp1 tag appears
> in the clone).

Sorry.  I did get confused.  And I now understand what happened.
git-clone works correctly.  What I did was "git-remote add svn
/.../path" followed by a "git-fetch svn".  Looks like that
one tag was not directly reachable in the history.  Running
"git-fetch -t svn" gave me the missing tags.

Sorry for the noise.




cheers, jerry
=====================================================================
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHCSxvIR7qMdg1EfYRAldVAJ4ns/X3JDrBnTft6JDEL5e8Tv80agCgvb59
/odKKLNtH2E1zB83pHg3Qdc=
=KkBD
-----END PGP SIGNATURE-----

      reply	other threads:[~2007-10-07 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07 18:23 Missing tags from git-clone, but not git-clone -l ? Gerald (Jerry) Carter
2007-10-07 18:58 ` Gerald (Jerry) Carter [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=47092C6F.7070108@samba.org \
    --to=jerry@samba.org \
    --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.