All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patricia Bittencourt Egeland <pbegeland@linea.gov.br>
Cc: git@vger.kernel.org
Subject: Re: tags not present in bare clone
Date: Mon, 23 Apr 2012 12:17:12 -0700	[thread overview]
Message-ID: <xmqqsjfui7gn.fsf@junio.mtv.corp.google.com> (raw)
In-Reply-To: <0BE9553B-C799-43D5-BA9A-28FC83CA0773@linea.gov.br> (Patricia Bittencourt Egeland's message of "Mon, 23 Apr 2012 11:28:32 -0600")

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.

    $ mkdir -p /var/tmp/junk && cd /var/tmp/junk
    $ git init src && cd src
    Initialized empty Git repository in /var/tmp/junk/src/.git/
    $ echo frotz >xyzzy && git add xyzzy && git commit -m initial
    [master (root-commit) b9c684a] initial
     1 file changed, 1 insertion(+)
     create mode 100644 xyzzy
    $ echo nitfol >xyzzy && git commit -a -m second
    [master 6982d52] second
     1 file changed, 1 insertion(+), 1 deletion(-)
    $ git tag -a -m 'First revision' v1.0 HEAD^
    $ git tag -a -m 'Second revision' v2.0 HEAD
    $ git for-each-ref
    6982d523f08b93dc6862ae80e80065b208d0ba85 commit	refs/heads/master
    33a6b315ffb461cba32d84ecd1692525a0846f5a tag	refs/tags/v1.0
    0d3f9dce20e28c6898423eb4a2c2010908e46a6c tag	refs/tags/v2.0
    $ cd ../ ;# back at /var/tmp/junk
    $ git clone src dst
    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

  reply	other threads:[~2012-04-23 19:17 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 [this message]
2012-04-23 19:19   ` Junio C Hamano
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=xmqqsjfui7gn.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.