From: Junio C Hamano <gitster@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Patricia Bittencourt Egeland <pbegeland@linea.gov.br>,
git@vger.kernel.org
Subject: Re: tags not present in bare clone
Date: Mon, 23 Apr 2012 12:19:57 -0700 [thread overview]
Message-ID: <xmqqobqii7c2.fsf@junio.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqsjfui7gn.fsf@junio.mtv.corp.google.com> (Junio C. Hamano's message of "Mon, 23 Apr 2012 12:17:12 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Patricia Bittencourt Egeland <pbegeland@linea.gov.br> writes:
>
>> I'm trying to create a bare clone from a regular repo (all
>> locally; in the same machine). However a tag created in the
>> regular repo can't be found in the fresh bare clone. I
>> expected that the tags would also be present just like anything
>> from "refs". Am I wrong about that?
>
> Reproduction recipe???
>
> A simple and straightforward attempt to reproduce what you said you did
> in your message does not exhibit any problem.
> ...
Oops, I forgot --bare.
> $ cd ../ ;# back at /var/tmp/junk
> $ git clone src dst
This should be "git --bare clone src dst" (or "git clone --bare src
dst").
But everything else in my previous message still holds true. I am
getting the identical output as the following.
> Cloning into 'dst'...
> done.
> $ cd dst
> $ git for-each-ref
> 6982d523f08b93dc6862ae80e80065b208d0ba85 commit refs/heads/master
> 6982d523f08b93dc6862ae80e80065b208d0ba85 commit refs/remotes/origin/HEAD
> 6982d523f08b93dc6862ae80e80065b208d0ba85 commit refs/remotes/origin/master
> 33a6b315ffb461cba32d84ecd1692525a0846f5a tag refs/tags/v1.0
> 0d3f9dce20e28c6898423eb4a2c2010908e46a6c tag refs/tags/v2.0
next prev parent reply other threads:[~2012-04-23 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 17:28 tags not present in bare clone Patricia Bittencourt Egeland
2012-04-23 19:17 ` Junio C Hamano
2012-04-23 19:19 ` Junio C Hamano [this message]
2012-04-23 20:43 ` Patricia Bittencourt Egeland
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=xmqqobqii7c2.fsf@junio.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pbegeland@linea.gov.br \
/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.