From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Cesar Eduardo Barros <cesarb@cesarb.net>, git@vger.kernel.org
Subject: Re: [PATCH] clone --mirror: avoid storing repeated tags
Date: Thu, 07 Aug 2008 21:57:08 -0700 [thread overview]
Message-ID: <7vej50gl3v.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0808080428520.9611@pacific.mpi-cbg.de.mpi-cbg.de> (Johannes Schindelin's message of "Fri, 8 Aug 2008 04:29:35 +0200 (CEST)")
Thanks for reporting and a quick fix.
This made me wonder if this relatively new "pack cloned refs" codepath has
funny interaction with --reference which is another user of add_extra_refs(),
but I think it is safe (we clear the real "extra" ones used during the
object transfer before calling write_remote_refs()).
next prev parent reply other threads:[~2008-08-08 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 0:59 1.6.0.rc2: Duplicated refs when using git clone --mirror Cesar Eduardo Barros
2008-08-08 2:29 ` [PATCH] clone --mirror: avoid storing repeated tags Johannes Schindelin
2008-08-08 4:57 ` Junio C Hamano [this message]
2008-08-08 6:41 ` Junio C Hamano
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=7vej50gl3v.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=cesarb@cesarb.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).