Paul Eggert wrote:
> > + ln -f "$file" "$file~" 2>/dev/null || cp -f "$file" "$file~" || {
>
> This will be problematic if the destination already exists, as the
> resulting permissions etc. may not be what the user intend. How about if
> we fall back on "mv -f" instead? Although this has the d
On Thu, Nov 16, 2017 at 2:37 AM, Bruno Haible wrote:
> Paul Eggert wrote:
>> > + ln -f "$file" "$file~" 2>/dev/null || cp -f "$file" "$file~" || {
>>
>> This will be problematic if the destination already exists, as the
>> resulting permissions etc. may not be what the user intend. How about if
>
On Thu, Nov 16, 2017 at 7:18 AM, Jim Meyering wrote:
> On Thu, Nov 16, 2017 at 2:37 AM, Bruno Haible wrote:
>> Paul Eggert wrote:
>>> > + ln -f "$file" "$file~" 2>/dev/null || cp -f "$file" "$file~" || {
>>>
>>> This will be problematic if the destination already exists, as the
>>> resulting per
On 11/16/2017 07:18 AM, Jim Meyering wrote:
Which is more important? (tempered with qualification that it probably
doesn't matter at all, since this is in the context of running a
program (gzexe) that is used very rarely, and even less frequently in
a context where ln fails to create a hard link)
