[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18141: 24.4.50; saving .gz file breaks file coding
From: |
Eli Zaretskii |
Subject: |
bug#18141: 24.4.50; saving .gz file breaks file coding |
Date: |
Fri, 08 Aug 2014 08:51:52 +0300 |
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: rgm@gnu.org, 18141@debbugs.gnu.org, vincent@vinc17.net, yamaoka@jpl.org
> Date: Thu, 07 Aug 2014 16:43:05 -0400
>
> > I think users generally expect this to be a transaction. And at least
> > on Posix platforms, where rename is an atomic operation, we can
> > achieve this, or come pretty close.
>
> I think the time-window is inevitable as long as we do "move first, then
> write the new file". Of course, we could do it the "precious"
> way instead (i.e. write the new file first and then do the needed
> link&unlink to move it into place).
Yes, I meant the latter method.
- bug#18141: 24.4.50; saving .gz file breaks file coding, (continued)
bug#18141: 24.4.50; saving .gz file breaks file coding, Stefan Monnier, 2014/08/06
- bug#18141: 24.4.50; saving .gz file breaks file coding, Eli Zaretskii, 2014/08/06
- bug#18141: 24.4.50; saving .gz file breaks file coding, Stefan Monnier, 2014/08/06
- bug#18141: 24.4.50; saving .gz file breaks file coding, Eli Zaretskii, 2014/08/07
- bug#18141: 24.4.50; saving .gz file breaks file coding, Stefan Monnier, 2014/08/07
- bug#18141: 24.4.50; saving .gz file breaks file coding, Eli Zaretskii, 2014/08/07
- bug#18141: 24.4.50; saving .gz file breaks file coding, Stefan Monnier, 2014/08/07
- bug#18141: 24.4.50; saving .gz file breaks file coding,
Eli Zaretskii <=
bug#18141: 24.4.50; saving .gz file breaks file coding, Glenn Morris, 2014/08/06
bug#18141: 24.4.50; saving .gz file breaks file coding, Glenn Morris, 2014/08/06