From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Thomas Nyberg <tomnyberg@gmail.com>,
David Turner <dturner@twopensource.com>
Cc: Stefan Beller <sbeller@google.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Corruption of branch?
Date: Mon, 14 Dec 2015 21:18:22 +0100 [thread overview]
Message-ID: <1450124302.16044.1.camel@kaarsemaker.net> (raw)
In-Reply-To: <566F1F96.4060806@gmail.com>
On ma, 2015-12-14 at 14:59 -0500, Thomas Nyberg wrote:
> I'm guessing you're looking for namecollisions of some kind?
I was thinking the same. Can you share the (sanitised) output of
git for-each-ref?
--
Dennis Kaarsemaker
www.kaarsemaker.net
next prev parent reply other threads:[~2015-12-14 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 17:40 Corruption of branch? Thomas Nyberg
2015-12-14 17:51 ` Stefan Beller
2015-12-14 18:08 ` Thomas Nyberg
2015-12-14 19:20 ` David Turner
2015-12-14 19:59 ` Thomas Nyberg
2015-12-14 20:18 ` Dennis Kaarsemaker [this message]
2015-12-14 20:33 ` Thomas Nyberg
2015-12-14 20:40 ` Dennis Kaarsemaker
2015-12-14 20:42 ` Junio C Hamano
2015-12-14 20:44 ` Thomas Nyberg
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=1450124302.16044.1.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=sbeller@google.com \
--cc=tomnyberg@gmail.com \
/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.