On Fri, Aug 30, 2019 at 9:25 PM Junio C Hamano wrote:
>
> But between these two:
>
> $ git clone --no-read-only-file-in-git https://github.com/foo/bar
> ...sightsee...
> $ rm -r bar
>
> to avoid "f" in "rm -r", vs.
>
> $ git clone https://github.com/foo/bar
>
Michal Suchánek writes:
>> But requiring an additional single "f" when doing "rm -rf .git"? Is
>> that realy too much of a hassle? The option "-f" is to allow people
>> deal with an unusual situation, while preventing everyday use from
>> doing something harmful unintendedly. And removing a cl
On Fri, 30 Aug 2019 09:38:11 -0700
Junio C Hamano wrote:
> Albert Vaca Cintora writes:
>
> > On Tue, Aug 27, 2019 at 9:35 PM Junio C Hamano wrote:
> >>
> >> Ah, your "rm" command needs to learn "-f" option, too, then?
> >
> > The whole point of this thread was to remove the need of -f forc
Albert Vaca Cintora writes:
> On Tue, Aug 27, 2019 at 9:35 PM Junio C Hamano wrote:
>>
>> Ah, your "rm" command needs to learn "-f" option, too, then?
>
> The whole point of this thread was to remove the need of -f forcing the
> removal.
OK, I misunderstood what you wanted to do.
If an implem
On Tue, Aug 27, 2019 at 9:35 PM Junio C Hamano wrote:
>
> Ah, your "rm" command needs to learn "-f" option, too, then?
The whole point of this thread was to remove the need of -f forcing the removal.
Albert Vaca Cintora writes:
> It "works" for some definition of work, but it asks for confirmation
> for every file, which is a pain. I'm on Linux.
Ah, your "rm" command needs to learn "-f" option, too, then?
On Mon, Aug 26, 2019 at 08:42:56PM +0200, Albert Vaca Cintora wrote:
> > Why don't you wrap your clone in a script that calls chmod -R u+w .git
> > after the clone? This seems like a pretty trivial approach regardless of
> > your workflow. This works in Linux, Mac, Windows (under cygwin-bash) and
On Mon, Aug 26, 2019 at 4:38 PM Junio C Hamano wrote:
>
> And directories (e.g. .git/objects/) are not made read-only for
> obvious reasons. Read-only files inside a writeable directory can
> be deleted just like read-write ones can be (iow, the "delete
> permission" comes from the "write permiss
On August 26, 2019 11:28 AM, Junio C Hamano wrote:
> "Randall S. Becker" writes:
>
> >> Sometimes I clone a repo just to grep for an error string and then I
> >> don't need it anymore, or I clone several repos until I find the one
> >> that contains what I want and delete the rest. Sometimes I wa
"Randall S. Becker" writes:
>> Sometimes I clone a repo just to grep for an error string and then I don't
>> need it anymore, or I clone several repos until I find the one that contains
>> what I want and delete the rest. Sometimes I want to write a patch for some
>> software I don't develop regu
Philip Oakley writes:
> Surely (?), if we are considering our stored revisions to be
> immutable, then removing the write bit is the right thing to do.
> If I understand correctly (*) we don't separate the delete permission
> from 'no-write' permissions, so the consequence will be that such
> fil
On August 25, 2019 3:59 PM, Albert Vaca Cintora wrote:
> To: Johannes Sixt
> On Sun, Aug 25, 2019 at 7:54 PM Johannes Sixt wrote:
> >
> > Am 23.08.19 um 22:43 schrieb Albert Vaca Cintora:
> > > However, I'm sure that a large percentage of developers out there
> > > will agree with me that having
On 25/08/2019 20:58, Albert Vaca Cintora wrote:
On Sun, Aug 25, 2019 at 7:54 PM Johannes Sixt wrote:
Am 23.08.19 um 22:43 schrieb Albert Vaca Cintora:
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
On Sun, Aug 25, 2019 at 7:54 PM Johannes Sixt wrote:
>
> Am 23.08.19 um 22:43 schrieb Albert Vaca Cintora:
> > 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 crea
Am 23.08.19 um 22:43 schrieb Albert Vaca Cintora:
> 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.
IMO, t
On Sun, Aug 25, 2019 at 1:59 PM Kevin Daudt 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 o
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 for
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
18 matches
Mail list logo
