Re: Creating remote branch called HEAD corrupts remote clones

On Thu, Jan 20, 2011 at 4:41 PM, Erik Faye-Lund [off-list ref] wrote:

On Thu, Jan 20, 2011 at 4:05 PM, Stephen Kelly [off-list ref] wrote:

quoted

Ok so there was some movement with the result that no one uses what was set up.

Presumably because git developers don't want a bug tracker.

So how can I ensure that this particular issue doesn't get lost? Is
there no way except hope that people get involved in fixing it
straight away, and fix it straight away before they forget about it?

You could always fix it yourself, and submit a patch.

Correct. That would be a big rampup though and I might give up, move
on or forget and then no one would do it because everyone has
forgotten about it. I mean that in the general sense of any bug that
gets posted to this mailing list.

But I'm not trying to change how git people work. I'm just trying to
discover what the states of a bug in git should be understood to be
after it is emailed to this list and before it's in master. So far it
seems there is only one intermediate state: "Limbo, maybe forgotten.
You should email the list again"

Thanks,

Steve.