-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Meyering <[EMAIL PROTECTED]> writes:
> > Hmmm... I wonder if it is possible to come up with a sanity.sh test case
> > for this one?
>
> I considered it but, dismissed it as infeasible.
> Of course, I would be happy to be proved wrong.
>
> It mig
> Hmmm... I wonder if it is possible to come up with a sanity.sh test case
> for this one?
I considered it but, dismissed it as infeasible.
Of course, I would be happy to be proved wrong.
It might work to use a tool like subterfugue, where you could presumably
cause to fail the first write after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Meyering <[EMAIL PROTECTED]> writes:
> "Mark D. Baushke" <[EMAIL PROTECTED]> wrote:
> > Your patch looks good to me. Go ahead and commit it.
>
> I've done so on the trunk.
> cvs1-11-x-branch too?
Yes, that would be good.
Hmmm... I wonder if it
"Mark D. Baushke" <[EMAIL PROTECTED]> wrote:
> Your patch looks good to me. Go ahead and commit it.
I've done so on the trunk.
cvs1-11-x-branch too?
___
Bug-cvs mailing list
Bug-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cvs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jim,
Your patch looks good to me. Go ahead and commit it.
-- Mark
Jim Meyering <[EMAIL PROTECTED]> writes:
> When a `login' commands leads to appending to .cvspass, that file is
> copied to a stream opened on a temporary file, and the ne
When a `login' commands leads to appending to .cvspass, that file is
copied to a stream opened on a temporary file, and the new entry is
appended. While failing to open or fwrite the temporary file evokes an
`error (1, ...', a failed fclose gets only a warning:
if ((fp = CVS_FOPEN (passfi
