From: Stephen Kelly <steveire@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: Creating remote branch called HEAD corrupts remote clones
Date: Wed, 27 Apr 2011 11:18:36 +0200 [thread overview]
Message-ID: <BANLkTimFas5YLt37RLuCppkQ4ZGhmj56Cg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinKDHM-RU2wqZECFcjQEoRWADnTGQ@mail.gmail.com>
On Tue, Apr 26, 2011 at 8:18 PM, Felipe Contreras
<felipe.contreras@gmail.com> wrote:
> On Tue, Apr 26, 2011 at 3:09 PM, Stephen Kelly <steveire@gmail.com> wrote:
>> Can git have a bug tracker please?
>
> So that you would feel comfortable that there would be a bug report
> gathering dust? Or that it's closed as invalid for lack of
> information?
If you believe that it is a foregone conclusion that that is the fate
of all bug trackers, and that that's a reasonable reason for git not
to have one, then you have had very different experiences to me.
I don't think there's more I can say than that.
>
>> This is another reminder to fix this bug which is otherwise untrackable.
>
> Let's imagine you are posting this to bugzilla: first question?
> How do you reproduce this?
My initial mail illustrated the problem as best I could:
http://thread.gmane.org/gmane.comp.kde.devel.pim/29534
>
> But I already asked you this[1], and you didn't reply. What should one
> assume but that you don't care enough to help get this fixed.
>
> [1] http://article.gmane.org/gmane.comp.version-control.git/165320
Someone else replied. Isn't that enough?
Other git developers confirmed it's probably an issue. Isn't that enough?
http://thread.gmane.org/gmane.comp.kde.devel.pim/29534/focus=165326
Anyway, we've had a work around in place since January. From the git
POV, this just falls through the cracks. Consider the bug marked as
can not reproduce/needs info/whatever you prefer. I'm outie.
Steve.
next prev parent reply other threads:[~2011-04-27 9:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 10:02 Creating remote branch called HEAD corrupts remote clones Stephen Kelly
2011-01-20 11:14 ` Stephen Kelly
2011-01-20 13:03 ` Thomas Rast
2011-01-20 15:05 ` Stephen Kelly
2011-01-20 15:41 ` Erik Faye-Lund
2011-01-20 16:00 ` Stephen Kelly
2011-01-20 17:32 ` Felipe Contreras
2011-01-20 19:21 ` Wesley J. Landaker
2011-01-20 19:53 ` Junio C Hamano
2011-01-20 20:38 ` Jeff King
2011-01-20 21:43 ` Junio C Hamano
2011-01-20 21:54 ` Jeff King
2011-01-20 23:52 ` Felipe Contreras
2011-01-21 17:37 ` Junio C Hamano
2011-01-22 12:46 ` Felipe Contreras
2011-02-20 13:17 ` Stephen Kelly
2011-04-26 12:09 ` Stephen Kelly
2011-04-26 18:18 ` Felipe Contreras
2011-04-27 9:18 ` Stephen Kelly [this message]
2011-04-27 9:48 ` Felipe Contreras
2011-04-27 11:29 ` Stephen Kelly
2011-04-27 11:32 ` Felipe Contreras
2011-04-27 11:37 ` Stephen Kelly
2011-04-27 12:26 ` Felipe Contreras
2011-04-27 12:21 ` Erik Faye-Lund
2011-04-27 12:49 ` Erik Faye-Lund
2011-05-02 19:26 ` Stephen Kelly
2011-05-02 19:43 ` Erik Faye-Lund
2011-05-03 17:54 ` Felipe Contreras
2011-05-03 18:08 ` Stephen Kelly
2011-05-03 19:20 ` Felipe Contreras
2011-05-04 12:35 ` Erik Faye-Lund
2011-05-09 7:51 ` [PATCH] only warn about ambiguous refs if stderr is a tty Erik Faye-Lund
2011-05-09 8:03 ` Jeff King
2011-05-09 8:41 ` Erik Faye-Lund
2011-05-09 10:32 ` Jeff King
2011-05-09 12:37 ` Erik Faye-Lund
2011-05-09 12:49 ` Jeff King
2011-05-09 16:33 ` Junio C Hamano
2011-05-09 22:09 ` Jeff King
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=BANLkTimFas5YLt37RLuCppkQ4ZGhmj56Cg@mail.gmail.com \
--to=steveire@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).