Ronnie Sahlberg <sahlberg@xxxxxxxxxx> writes: > I don't think we need to do that. > That would imply that we would need to be able to also allow reading > the content of a badly named ref. > Currently a badly named ref can not be accessed by any function except > git branch -D <badlynamedref> which contains the special flag that > allows locking it eventhough the ref has an illegal name. > > So no one else should be able to read or modify the ref at all. OK. > I think it is sufficient for this case to just have the semantics > "just delete it, I don't care what it used to point to." for this > special case git branch -D <badrefname> > so therefore since it is not the content of the ref but the name of > the ref itself we have a problem with I don't think we need to read > the old value or verify it. -- 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