Re: Deleting the "current" branch in remote bare repositories

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 09, 2009 at 01:28:43PM -0500, Jeff King wrote:

> Here are two reasons why we might not want to conflate the two safety
> valves:

Argh, sorry, I'm an idiot. For some reason when I saw
"receive.denyDeleteCurrent" I read "receive.denyCurrentBranch" (and if
you look carefully in the thread, I even _typed_ it wrong, too!).

So I read your emails as "we should put this new safety valve under the
same option as the other one" which you are of course not proposing at
all.

Please disregard this last email (and the one before it, but you have
already responded to that ;) ). And I will ask a doctor to remove the brain
tumor that is clearly inhibiting my reading comprehension.

-Peff
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux