On Sat, Mar 1, 2014 at 1:58 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Karsten Blees <karsten.blees@xxxxxxxxx> writes: > >>> If you are on a case-insensitive filesystem, or work on a cross-platform >>> project, ensure that you avoid ambiguous refs. Problem solved. >>> >> >> So its OK to lose data if you accidentally use an ambiguous ref? I >> cannot believe you actually meant that. > > I think he meant what he said: "you avoid ambiguous refs". He did > not say "it is not Git's business to help you doing so". > > I think it is prudent to warn in the end-user facing layer (read: do > not touch refs.c to implement something like that) when the user > creates "refs/heads/Next" when there already is "refs/heads/next", > and I further think it would make sense to do so even on case > sensitive platforms. That does not help when the user creates "next" and pulls "Next" from elsewhere, does it? -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html