Had a quick look at some old notes. If someone is looking for a
possible code fix in RCS 5.8: try adding an fflush of the "stream" of
the "fro" struct to the macro "fro_bob" in b-fro.h. Something like
this perhaps:
#define fro_bob(f) do { if (STDIO_P(f)) fflush((f)->stream); fro_move (f,
0)
As previously mentioned in
http://cygwin.com/ml/cygwin/2014-02/msg00678.html
the failure mechanism in RCS 5.8 is described in
http://cygwin.com/ml/cygwin/2012-09/msg00331.html
No response from Dr. Zell.
RCS bug report:
http://savannah.gnu.org/bugs/index.php?41707
So far n
Achim Gratz NexGo.DE> writes:
> Make sure you test the stdio code path, if they changed the sematics of
> RCS_MEM_LIMIT again, then you may need a different demonstrator to switch to
> stdio from the usual mmap code path.
For grins I just built RCS 5.9.2, fixed a bug in the btdt program so it
wou
Warren Young etr-usa.com> writes:
> It's not a bug, it's a buffer size choice made with the rcs 5.8 release,
> which affects Cygwin for reasons unknown.
It is a bug in the "stdio" code path, independently of buffer size. That
bug doesn't trigger on GNU/Linux, btw.
> I built 5.9.2 under Cygwin
On 4/16/2014 10:09, tedno...@bellsouth.net wrote:
I just hit the worst Cygwin bug I've encountered, the RCS bug which
silently corrupts text files > 256K.
It's not a bug, it's a buffer size choice made with the rcs 5.8 release,
which affects Cygwin for reasons unknown.
GNU rcs 5.9.2 changed
In message
you write:
>RCS does a great job for smaller projects when I don't need the
>overhead of any of the popular larger systems. It has saved me many
>times when I'm working on a short document or a set of scripts on my
>desktop machine.
>
>I'd miss it if it were removed simply due to the l
RCS does a great job for smaller projects when I don't need the
overhead of any of the popular larger systems. It has saved me many
times when I'm working on a short document or a set of scripts on my
desktop machine.
I'd miss it if it were removed simply due to the lack of handling
10Meg of diff
In message <87bnw12nuu.fsf@Rainer.invalid>you write:
>tedno...@bellsouth.net writes:
>> Just for the record, the suggested env var fix
>>
>> RCS_MEM_LIMIT=0
>>
>> to "force stdio" does not work for me, but the
>
>That was never suggested as a fix, but to show that the problem occurs
>with files muc
tedno...@bellsouth.net writes:
> Just for the record, the suggested env var fix
>
> RCS_MEM_LIMIT=0
>
> to "force stdio" does not work for me, but the
That was never suggested as a fix, but to show that the problem occurs
with files much less than 256kiB size when forcing the code path through
std
I just hit the worst Cygwin bug I've encountered, the RCS bug which
silently corrupts text files > 256K. That's the last thing I expect
from a version control system!
After some moments of panic, I was able to retrieve a good copy from
backups, but have lost my revision history.
Anyway, I immedi
10 matches
Mail list logo
