All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Stephen Bash <bash@genarts.com>
Cc: git@vger.kernel.org
Subject: Re: Tags, Grafts, and Clones, oh my!
Date: Fri, 20 Aug 2010 11:45:04 +0530	[thread overview]
Message-ID: <20100820061459.GB12794@kytes> (raw)
In-Reply-To: <15347445.117294.1282265669453.JavaMail.root@mail.hq.genarts.com>

Hi Stephen,

Stephen Bash writes:
> Unfortunately I'm running into a problem with cloning the resulting repository.  Any git tags that are not associated with a live branch are declared invalid:
> 
>    error: refs/tags/tagFoo does not point to a valid object!
> 
> I've now reproduced this issue in micro (much easier to work with than the 20k commits in the real repo), and it does go away if I git checkout -b branchFoo tagFoo before cloning the repository.  I've examined the source repository, and the tag appears valid to me, as does the commit it points to.  The first error I see is during the clone.
> 
> Does this situation make sense to anyone?  If it's a potential bug (rather than user error), I can submit my testcase.  I'm currently working with git 1.7.2.1 on MacOS 10.6.4.

It seems too vague to me. Can you submit your testcase? Perhaps we can
work from there?

-- Ram

  reply	other threads:[~2010-08-20  6:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29380346.117285.1282264933599.JavaMail.root@mail.hq.genarts.com>
2010-08-20  0:54 ` Tags, Grafts, and Clones, oh my! Stephen Bash
2010-08-20  6:15   ` Ramkumar Ramachandra [this message]
2010-08-20 13:00     ` Stephen Bash
2010-08-20 13:39       ` Ramkumar Ramachandra
2010-08-20 14:40         ` Stephen Bash
2010-08-20 19:08           ` refs/original breaks git-clone for tags (was Re: Tags, Grafts, and Clones, oh my!) Stephen Bash
2010-09-07 23:14             ` refs/original breaks git-clone for tags Jonathan Nieder

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=20100820061459.GB12794@kytes \
    --to=artagnon@gmail.com \
    --cc=bash@genarts.com \
    --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.