If it should become necessary to mark a branch read-only, I would suggest the following:
Rename it as a tag; that's effectively what it has become - tags should be immutable. or Rename it to xxx_READ_ONLY In each case it would probably be worthwhile to add a README file to explain the rationale (and point to the mail thread). On 27 November 2013 12:49, Jeff MAURY <[email protected]> wrote: > Done > > Jeff > > > On Wed, Nov 27, 2013 at 1:44 PM, Emmanuel Lécharny <[email protected]>wrote: > >> Le 11/27/13 1:29 PM, Jeff MAURY a écrit : >> > Hello, >> > >> > I've rebased 2.0.8 into 2.0 and pushed it to the server. >> >> Ok, thanks. >> >> > Still have to either delete 2.0.8 branch or put it read only (it is >> > possible to do it with a hook but it seems it is not possible to push a >> > hook) >> >> Just delete it. It's useless. >> >> -- >> Regards, >> Cordialement, >> Emmanuel Lécharny >> www.iktek.com >> >> > > > -- > Jeff MAURY > > > "Legacy code" often differs from its suggested alternative by actually > working and scaling. > - Bjarne Stroustrup > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.twitter.com/jeffmaury
