From: Junio C Hamano <junkio@cox.net>
To: Uwe Zeisberger <zeisberg@informatik.uni-freiburg.de>
Cc: git@vger.kernel.org
Subject: Re: HEAD branch duplicated in remotes/origin
Date: Thu, 08 Jun 2006 09:39:48 -0700 [thread overview]
Message-ID: <7vpshj8uuj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060608123337.GA12456@informatik.uni-freiburg.de> (Uwe Zeisberger's message of "Thu, 8 Jun 2006 14:33:38 +0200")
Uwe Zeisberger <zeisberg@informatik.uni-freiburg.de> writes:
> I wonder if this is easier not to add the other duplicate.
Unfortunately the above is probably easier. The other duplicate
is coming from the lowlevel code that makes sure each of the
fetch-pack parameters is not used to match more than once. We
should fix it eventually, though.
prev parent reply other threads:[~2006-06-08 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 7:38 HEAD branch duplicated in remotes/origin Uwe Zeisberger
2006-06-08 8:17 ` Junio C Hamano
2006-06-08 12:33 ` Uwe Zeisberger
2006-06-08 16:39 ` Junio C Hamano [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=7vpshj8uuj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=zeisberg@informatik.uni-freiburg.de \
/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).