On Sun, Aug 25, 2019 at 1:59 PM Kevin Daudt <me@xxxxxxxxx> wrote: > > On Fri, Aug 23, 2019 at 10:43:45PM +0200, Albert Vaca Cintora wrote: > > Hi git folks, > > > > Honestly I'm not aware of the reason behind .git being read-only, but > > I'm sure there is one. > > > > However, I'm sure that a large percentage of developers out there will > > agree with me that having to use force (-f) to delete every cloned > > repo is annoying, and even worse, it creates the bad habit of always > > force-deleting everything. > > > > Would you find reasonable to add an option to keep .git writable on > > cloned repos? > > > > PS: I'm not subscribed to the list, so please CC me on replies. > > > > Thanks! > > Albert > > To clarify, you are probably referring to things like pack-files, which > are created read-only. Most files / directories in .git are writable. > > It think this is already quite old behavior and I could not find any > reference as to why this is done. Indeed, not all files in .git are read-only. I'm talking about those which are. On Sun, Aug 25, 2019 at 1:59 PM Kevin Daudt <me@xxxxxxxxx> wrote: > > On Fri, Aug 23, 2019 at 10:43:45PM +0200, Albert Vaca Cintora wrote: > > Hi git folks, > > > > Honestly I'm not aware of the reason behind .git being read-only, but > > I'm sure there is one. > > > > However, I'm sure that a large percentage of developers out there will > > agree with me that having to use force (-f) to delete every cloned > > repo is annoying, and even worse, it creates the bad habit of always > > force-deleting everything. > > > > Would you find reasonable to add an option to keep .git writable on > > cloned repos? > > > > PS: I'm not subscribed to the list, so please CC me on replies. > > > > Thanks! > > Albert > > To clarify, you are probably referring to things like pack-files, which > are created read-only. Most files / directories in .git are writable. > > It think this is already quite old behavior and I could not find any > reference as to why this is done.
