1 |
On Fri, Jun 15, 2012 at 1:08 PM, Mike Frysinger <vapier@g.o> wrote: |
2 |
> On Friday 15 June 2012 12:54:16 Michał Górny wrote: |
3 |
>> On Fri, 15 Jun 2012 11:11:44 -0400 Michael Orlitzky wrote: |
4 |
>> > On 06/15/12 09:32, Michał Górny wrote: |
5 |
>> > > It is a little confusing when the function reports .a removal when |
6 |
>> > > no such file exists. Also, explain why the file is removed. |
7 |
>> > |
8 |
>> > Why keep the "-f"? |
9 |
>> |
10 |
>> For rm? |
11 |
>> |
12 |
>> -f, --force |
13 |
>> ignore nonexistent files and arguments, never prompt |
14 |
>> |
15 |
>> The second part is still valid. |
16 |
> |
17 |
> i think his point was that since you just did a [[ -f ]] test, there shouldn't |
18 |
> really be any cases where the rm would fail, so you could change the `rm -f` |
19 |
> to `rm || die` ... |
20 |
> -mike |
21 |
|
22 |
Just because you tested doesn't make the race go away; its not like |
23 |
the fs has locks. |
24 |
|
25 |
-A |