A sub-folder has no meaning because this is just a git branch is just a virtual concept on top of sources. The problem was because of the double existence of 2.0 and 2.0.8 branches.
Jeff On Fri, Nov 29, 2013 at 4:03 AM, Emmanuel Lécharny <[email protected]>wrote: > Le 11/28/13 10:27 PM, sebb a écrit : > > 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. > > Certainly not a tag. A tag is a released version. > > I'd rather move the branch to a "deceased" sub-folder if necessary. > > > -- > 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
