[ANNOUNCEMENT] Updated: rcs-5.10.1-1

RCS has been updated to the latest upstream release 5.10.1, the list of changes and fixes can be viewed on the project homepage. https://www.gnu.org/software/rcs/rcs.html -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing

[ANNOUNCEMENT] Updated: rcs-5.10.0-1

RCS has been updated to the latest upstream release 5.10.0, the list of changes and fixes can be viewed on the project homepage. https://www.gnu.org/software/rcs/rcs.html -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing

Re: RCS?

Sorry to jump the gun, I found cpp, too. -Bill On 6/15/2020 10:10 AM, Bill Coffin wrote: It turned out to be easier than that.  I just re-ran the installer and added the RCS package.  Works fine!  I also found "make" easily enough.  But which package contains cpp (the C preprocesso

Re: RCS?

It turned out to be easier than that.  I just re-ran the installer and added the RCS package.  Works fine!  I also found "make" easily enough.  But which package contains cpp (the C preprocessor, not the C++ thing). Thanks,   Bill On 6/14/2020 5:23 PM, Eliot Moss wrote: Rebuild t

Re: RCS?

Rebuild the package from source. 32 and 64 but Cygwin have different binary models. Sent from my iPhone > On Jun 14, 2020, at 8:05 PM, Bill Coffin wrote: > > I've been using RCS for many years in an older cygwin running, most > recently, on Windows 10. For some

Re: RCS?

On 6/14/2020 8:05 PM, Bill Coffin wrote: I've been using RCS for many years in an older cygwin running, most recently, on Windows 10.  For some reason, my cygwin installation went nuts so I downloaded and installed cygwin64.  cygwin64 works great but doesn't have RCS. RCS is availa

RCS?

I've been using RCS for many years in an older cygwin running, most recently, on Windows 10.  For some reason, my cygwin installation went nuts so I downloaded and installed cygwin64.  cygwin64 works great but doesn't have RCS.  I've searched the net and all other sources (the

Re: RCS Error report - Couldn't compute FAST_CWD pointer

Am 07.09.2018 um 15:04 schrieb Theresa Campbell: . 0 [main] diff 620 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com done Kindest Regards, Theresa Campbell https://cygwin.com/faq.html#faq.using.fixing

RCS Error report - Couldn't compute FAST_CWD pointer

>> . 0 [main] diff 620 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com done Kindest Regards, Theresa Campbell For the BEST response from AUC support, please send e-mails to supp...@admins.com

Re: Unable to use Cygwin RCS commands in Windows Emacs

d directly from a Windows > command > line and moreover can not be invoked by a Windows (not Cygwin) Emacs (25.2 > currentlly). I don't use RCS, but have other Cygwin tools successfully with the Windows port of emacs. The advice below fixes your problem: if a program is an execu

Re: Unable to use Cygwin RCS commands in Windows Emacs

On Freitag, 22. September 2017 04:26:47 CEST David Standish wrote: > I managed to get windows emacs to work with cygwin rcs. > > Apart from rcs.exe, the other rcs commands are shell scripts that > invoke rcs.exe. > > Create a modified version of vc-rcs.el > replacing the va

Re: Unable to use Cygwin RCS commands in Windows Emacs

I managed to get windows emacs to work with cygwin rcs. Apart from rcs.exe, the other rcs commands are shell scripts that invoke rcs.exe. Create a modified version of vc-rcs.el replacing the various vc-do-command's with alternate ones that use rcs.exe directly, For example: (apply &

Re: Unable to use Cygwin RCS commands in Windows Emacs

Am Mittwoch, 20. September 2017, 23:01:48 CEST schrieb cyg Simple: > I suggest you ask your Windows Emacs support list. They would have the > most users with suggestions. Thanks, yes, will do. Regards, Heinz -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: Unable to use Cygwin RCS commands in Windows Emacs

Am Mittwoch, 20. September 2017, 22:40:53 CEST schrieb Brian Inglis: > > Tried creating shortcuts to the commands in $HOME/bin/, running > C:\Cygwin\bin\sh /bin/cmd %*, and adding $HOME/bin to the start of your > Windows PATH? Thanks, but that doesn't work. Emacs does not see shortcuts as executa

Re: Unable to use Cygwin RCS commands in Windows Emacs

On 9/20/2017 4:12 PM, Heinz Werner Kramski-Grote wrote: > At some point in history, /usr/bin/co, /usr/bin/ci, /usr/bin/rlog etc. turned > from .exe into shell scripts, which are now wrappers for the main program > /usr/bin/rcs.exe. > > However, these shell scripts can not be called directly fro

Re: Unable to use Cygwin RCS commands in Windows Emacs

called directly from a Windows > command > line and moreover can not be invoked by a Windows (not Cygwin) Emacs (25.2 > currentlly). > > Windows Emacs expects external Windows commands/binaries like co, ci, rlog, > etc. to exist somewhere in the PATH. The commands to be invoke

Unable to use Cygwin RCS commands in Windows Emacs

Windows (not Cygwin) Emacs (25.2 currentlly). Windows Emacs expects external Windows commands/binaries like co, ci, rlog, etc. to exist somewhere in the PATH. The commands to be invoked for version control with RCS are hardcoded into "C:\Program Files\emacs-25.2\share\emacs \25.2\lisp\

[ANNOUNCEMENT] [Updated] rcs-5.9.4

RCS has been updated to the latest upstream release 5.9.4. No functional changes are expected from that update. From the upstream announcement: --8<---cut here---start->8--- release notes: A small portability fix, thanks to Christian Wagner.

[ANNOUNCEMENT] Updated: rcs-5.9.3

This release brings RCS to version 5.9.3 for both architectures. A slightly modified version of the patch for the RCS work file corruption problem is now included in the upstream sources along with a test, so no Cygwin specific patches need to be applied. --8<---cut h

Re: Gold star Re: [ANNOUNCEMENT] Updated: rcs-5.9.2

Keith Christian wrote: > I use RCS every work day, it's a small, fast, flexible productivity > tool, sometimes with a timed loop to save rapid editing sessions when > I'm brainstorming.maybe that edit a few hours ago was worth saving > after all, and with RCS I can get

Re: Gold star Re: [ANNOUNCEMENT] Updated: rcs-5.9.2

I use RCS every work day, it's a small, fast, flexible productivity tool, sometimes with a timed loop to save rapid editing sessions when I'm brainstorming.maybe that edit a few hours ago was worth saving after all, and with RCS I can get it back. Thank you for updating it and be

Re: Gold star Re: [ANNOUNCEMENT] Updated: rcs-5.9.2

> On Thu, Jul 03, 2014 at 07:59:42PM +0200, Achim Gratz wrote: > >This release brings RCS to version 5.9.2 for both architectures and > >includes a patch for the RCS work file corruption problem that has been > >discussed on the Cygwin mailing list and reported to rcs-bugs

Gold star Re: [ANNOUNCEMENT] Updated: rcs-5.9.2

On Thu, Jul 03, 2014 at 07:59:42PM +0200, Achim Gratz wrote: >This release brings RCS to version 5.9.2 for both architectures and >includes a patch for the RCS work file corruption problem that has been >discussed on the Cygwin mailing list and reported to rcs-bugs: Could we get a gold

[ANNOUNCEMENT] Updated: rcs-5.9.2

This release brings RCS to version 5.9.2 for both architectures and includes a patch for the RCS work file corruption problem that has been discussed on the Cygwin mailing list and reported to rcs-bugs: http://article.gmane.org/gmane.comp.version-control.rcs.bugs/2772 Thanks to Don Hatch for a

RE: Wow, just hit RCS bug (attn: Dr Volker Zell)

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

RE: Wow, just hit RCS bug (attn: Dr Volker Zell)

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

Re: Wow, just hit RCS bug (attn: Dr Volker Zell)

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 p

Re: Wow, just hit RCS bug (attn: Dr Volker Zell)

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,

Re: Wow, just hit RCS bug (attn: Dr Volker Zell)

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

Re: Wow, just hit RCS bug

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

Re: Wow, just hit RCS bug

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 ha

Re: Wow, just hit RCS bug

a fix, but to show that the problem occurs >with files much less than 256kiB size when forcing the code path through >stdio (which is what the "0" setting does). The RCS test suite passes >on Cygwin since it never actively tests this code path. > >http://thread.gmane.org/gma

Re: Wow, just hit RCS bug

ing the code path through stdio (which is what the "0" setting does). The RCS test suite passes on Cygwin since it never actively tests this code path. http://thread.gmane.org/gmane.os.cygwin/142346 > RCS_MEM_LIMIT=10240 > > to allow 10megs of diffs does.. Which will fail once

Wow, just hit RCS bug

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 histor

Re: checking in >= 256k file fatally corrupts rcs file

This is an additional comment on the thread starting with http://cygwin.com/ml/cygwin/2013-10/msg00086.html Recently I was bitten again by this RCS 5.8 bug after I failed to keep RCS at version 5.7 during a Cygwin update. The failure mechanism is described in http://cygwin.com/ml

Re: checking in >= 256k file fatally corrupts rcs file

problem with file size corrupting the file - on several occasions I have checked in a file and lost roughly half of it. As RCS only stores the last version in its entirety and deltas against that version to create prior versions, losing part of the current version results in a completely corrupt f

Re: checking in >= 256k file fatally corrupts rcs file

Ryan Johnson writes: > So in other words, a misguided performance optimization [1] that > almost certainly has little measurable impact on performance [2] has > introduced a silent data corruption bug (or tickled a latent one > somewhere else). Lovely. It is not the performance optimization that i

Re: checking in >= 256k file fatally corrupts rcs file

ot have the broken version on my system at all-- then I can relax and not be continually worrying about whether each different way I (or anyone else including root daemons) use rcs is going to somehow circumvent the environment variable and destroy more work. > > We're talki

Re: checking in >= 256k file fatally corrupts rcs file

ke a 5.9 that's identical to 5.7, If a new Cygwin package had to come out based on 5.7, it would be called 5.7-12, not 5.9. GNU rcs 5.9 already exists. (The current upstream release is 5.9.1.) Cygwin packages generally leave the upstream revision numbers unmolested. Or, just roll a 5.8-

Re: checking in >= 256k file fatally corrupts rcs file

On 08/10/2013 7:48 PM, Warren Young wrote: On 10/8/2013 04:22, Don Hatch wrote: Checking in a text file of size >= 256k corrupts the rcs file, irretrievably losing most of the contents It's documented in the rcs NEWS file: - Env var RCS_MEM_LIMIT controls stdio threshold.

Re: checking in >= 256k file fatally corrupts rcs file

win package system allows one to mark 5.8-1 as obsolete, but I don't know if it can be told "and downgrade to 5.7-11". If not, can we make a 5.9 that's identical to 5.7, If a new Cygwin package had to come out based on 5.7, it would be called 5.7-12, not 5.9. GNU r

Re: checking in >= 256k file fatally corrupts rcs file

On Tue, Oct 08, 2013 at 07:30:40PM -0600, Warren Young wrote: > On 10/8/2013 18:30, Don Hatch wrote: > >On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote: > >>On 10/8/2013 04:22, Don Hatch wrote: > >>> > >>>Checking in a text file

Re: checking in >= 256k file fatally corrupts rcs file

On 10/8/2013 20:08, Gary Johnson wrote: There was a discussion around March 27, 2012, about another change in the behavior of RCS between 5.7 and 5.8. It appears that someone decided to make some sweeping "improvements" to RCS and broke a few things along the way. GNU rcs 5.7 was r

Re: checking in >= 256k file fatally corrupts rcs file

On 2013-10-08, Warren Young wrote: > On 10/8/2013 18:30, Don Hatch wrote: > >On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote: > >>On 10/8/2013 04:22, Don Hatch wrote: > >>> > >>>Checking in a text file of size >= 256k > >>&g

Re: checking in >= 256k file fatally corrupts rcs file

On 10/8/2013 18:30, Don Hatch wrote: On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote: On 10/8/2013 04:22, Don Hatch wrote: Checking in a text file of size >= 256k corrupts the rcs file, irretrievably losing most of the contents It's documented in the rcs NEWS file: Th

Re: checking in >= 256k file fatally corrupts rcs file

On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote: > On 10/8/2013 04:22, Don Hatch wrote: > > > >Checking in a text file of size >= 256k > >corrupts the rcs file, irretrievably losing most of the contents > > It's documented in the rcs NEWS fil

Re: checking in >= 256k file fatally corrupts rcs file

On 10/8/2013 04:22, Don Hatch wrote: Checking in a text file of size >= 256k corrupts the rcs file, irretrievably losing most of the contents It's documented in the rcs NEWS file: - Env var RCS_MEM_LIMIT controls stdio threshold. For speed, RCS uses memory-based routines f

[ANNOUNCEMENT] Updated: rcs-5.8.2-1: The Revision Control System

Hi A new version of 'rcs' has been uploaded to a server near you. o Update to latest upstream release o Build for cygwin 1.7.18 with gcc-4.5.3 rcs NEWS: = - Bugs fixed - Wrong symbolic name dereference RCS 5.8 introduced a bug whereby commands would i

RE: [ANNOUNCEMENT] Updated: rcs-5.8.1-1: The Revision Control System

Dear Dr. Zell, > [ANNOUNCEMENT] Updated: rcs-5.8.1-1: The Revision Control System Do you perhaps know whether this version fixes the file corruption problem noticed earlier on this list for 5.8, or should we stay with 5.7 to avoid corrupting large RCS files? Short problem description (wha

[ANNOUNCEMENT] Updated: rcs-5.8.1-1: The Revision Control System

Hi A new version of 'rcs' has been uploaded to a server near you. o Update to latest upstream release o Build for cygwin 1.7.16 with gcc-4.5.3 o Uses cygport-0.11.0 for .hint files generation o debuginfo package included rcs NEWS: = - Bugs fixed - Debug outp

Re: RCS file corruption.

Greetings, Richard Gribble! >> > One thing I may have failed to mention is that (anecdotaly - I didn't >> > take copious notes) the problem usually appeared when I had lines with >> > two "^M"s at the end.  I suspect this happens because sometimes I edit >> > the files on my Linux box and sometime

RE: RCS file corruption.

Brian Wilson wrote: > From what I've read in this discussion, I think the issue is that > the '^M' characters may not be seen by RCS as an EOL. The problem occurs in a loop that copies one character at a time to move the entire content of the work file into the new R

Re: RCS file corruption.

> I suspect this happens because sometimes I edit the files on my Linux box and sometimes on my Windows box. If I remember correctly, RCS (and the earlier SCCS systems) were designed to work with source code (i.e. text files). They determined file changes based on lines added or deletes

Re: RCS file corruption.

On Thu, Jun 21, 2012 at 4:44 PM, Andrey Repin wrote: > > Greetings, Richard Gribble! > > > One thing I may have failed to mention is that (anecdotaly - I didn't > > take copious notes) the problem usually appeared when I had lines with > > two "^M"s at the end.  I suspect this happens because some

Re: RCS file corruption.

Greetings, Richard Gribble! > One thing I may have failed to mention is that (anecdotaly - I didn't > take copious notes) the problem usually appeared when I had lines with > two "^M"s at the end.  I suspect this happens because sometimes I edit > the files on my Linux box and sometimes on my Wind

Re: RCS file corruption.

On Thu, Jun 21, 2012 at 5:05 AM, Wagemans, Peter wrote: > > > Richard Gribble wrote: > > > I have experienced this problem several times.  In my case it seemed > > to be a problem between 'Unix' and 'DOS' files.  In each case, I > > have been ab

RE: RCS file corruption.

Richard Gribble wrote: > I have experienced this problem several times. In my case it seemed > to be a problem between 'Unix' and 'DOS' files. In each case, I > have been able to fix it by editing the RCS file using vim and > deleting all the extraneous carriag

Re: RCS file corruption.

> I have experienced this problem several times. In my case it seemed > to be a problem between 'Unix' and 'DOS' files. In each case, I have > been able to fix it by editing the RCS file using vim and deleting all > the extraneous carriage returns - :%s/^M$/

Re: RCS file corruption.

I have experienced this problem several times.  In my case it seemed to be a problem between 'Unix' and 'DOS' files.  In each case, I have been able to fix it by editing the RCS file using vim and deleting all the extraneous carriage returns - :%s/^M$// Sometimes I've ha

Re: rcs 5.8-1 checks out wrong version of file when using similar mark symbols

cmp from the start. > > > > I don't know, the "original" authors seem to have gotten it right, > > as version 5.7 works correctly on my Fedora system, and the function > > in question was added between versions 5.7 and 5.8. > > What are you trying to s

Re: rcs 5.8-1 checks out wrong version of file when using similar mark symbols

t;original" authors seem to have gotten it right, > as version 5.7 works correctly on my Fedora system, and the function > in question was added between versions 5.7 and 5.8. What are you trying to say here? That whoever it was that brought rcs from 5.7 to 5.8 are a bunch of idiots? I&

Re: rcs 5.8-1 checks out wrong version of file when using similar mark symbols

On 2012-03-27, Peter Rosin wrote: > But the point still stands, don't assume the original authors were > idiots, and dig into the reasons for them to not having used > strcmp from the start. I don't know, the "original" authors seem to have gotten it right, as version 5.7 works correctly on my Fed

Re: rcs 5.8-1 checks out wrong version of file when using similar mark symbols

Peter Rosin skrev 2012-03-27 10:11: > But...careful! You have to assume that the original authors were not > idiots! Maybe the obvious strcmp was not used for a *good* reason? I > can't tell if d->meaningful is guaranteed to be zero-terminated from the > limited context, but it sure is suspect.

Re: rcs 5.8-1 checks out wrong version of file when using similar mark symbols

Csaba Raduly skrev 2012-03-27 09:37: > On Mon, Mar 26, 2012 at 9:29 PM, Richard Gribble wrote: >> Using rcs 5.8-1: >> >> Synopsis: >>Given two mark symbols, abc (version 1.1) and abcd (version 1.2), >>executing "co -rabc " will check out version

Re: rcs 5.8-1 checks out wrong version of file when using similar mark symbols

On Mon, Mar 26, 2012 at 9:29 PM, Richard Gribble wrote: > Using rcs 5.8-1: > > Synopsis: >    Given two mark symbols, abc (version 1.1) and abcd (version 1.2), >    executing "co -rabc " will check out version 1.2, when it >    should check out version 1.1. > >

Re: rcs 5.8-1 corrupt files?

On 11/12/2011 08:24, Jay E. wrote: > Suspected line-ender problem. > Started over and used 'flip' to go with unix line-ender. > Same problems. > BUT it looks like the DOS lime ender was added after the flip by ci, or co. It looks like the line-ends are getting flipped

rcs 5.8-1 corrupt files?

rcs 5.8-1 A problem with rcs. - corrupt files.. Here is the sequence: Create a 'hello world' file using vi. Check in a file. ci -u sam Check out the file co -l sam get error when doing rlog on the next ci of the file. example: rlog sam rlog: RCS/sam,v:31: junk

[ANNOUNCEMENT] Updated: rcs-5.7-11: The Revision Control System

Hi A new version of 'rcs' has been uploaded to a server near you. o Fixed bug for rcsdiff not finding co (see http://cygwin.com/ml/cygwin/2010-05/msg00667.html) CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announ

R: [Packaging error] octave-forge-20090607-2 has a RCS subdirectory

--- Ven 28/5/10, Dr. Volker Zell ha scritto: > Hi > > octave-forge-20090607-2 has the following subdirectory > > o /usr/share/octave/packages/gsl-1.0.8/doc/RCS > > which probably shouldn't be there. > > Ciao >   Volker > Oh nice, it is a fault of up

[Packaging error] octave-forge-20090607-2 has a RCS subdirectory

Hi octave-forge-20090607-2 has the following subdirectory o /usr/share/octave/packages/gsl-1.0.8/doc/RCS which probably shouldn't be there. Ciao Volker -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: rcsdiff in RCS version 5.7 seems broken

> Volker Zell writes: > I can confirm this, but do not understand whats going on. By the way, > when you do rcsdiff and co is in the same directory as the source file > it workks. I found the culprit. A new version is already uploaded. Ciao Volker -- Problem reports:

Re: rcsdiff in RCS version 5.7 seems broken

>>>>> R DeFuria writes: > Hello, > Yesterday, I (re)ran v 2.697 of Cygwin's setup.exe to update anything > that was out of date. > Among other things, it updated RCS. > Now, the rcsdiff command no longer works on my box: >

[ANNOUNCEMENT] Updated: rcs-5.7-10: The Revision Control System

Hi A new version of 'rcs' has been uploaded to a server near you. o Build for cygwin 1.7 with gcc-4 CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://

[1.7] RCS - co -l fails if *,v not owned by user -

RCS co -l fails if the ,v file is not owned by the user. I get a permission denied error. In my case, the RCS directory is on samba. It seems to fix it if in conf.h I change #define bad_b_rename 1 The flag makes it delete the target(*,v) before renaming the work file (,*,v -> *,v) Tha

Re: [1.7] RCS - co -l fails if *,v not owned by user -

On 11/03/2009 08:33 PM, Yeng Chen wrote: RCS co -l fails if the ,v file is not owned by the user. I get a permission denied error. In my case, the RCS directory is on samba. It seems to fix it if in conf.h I change #define bad_b_rename 1 The flag makes it delete the target(*,v) before renaming

[ANNOUNCEMENT] Updated: rcs-5.7-4: The Revision Control System

Hi A new version of `rcs' has been uploaded to a server near you. Cygwin NEWS: o Maintainer change o Switched to cygport build framework o Documentation and manual pages now under /usr/share/{man/doc} hierarchy o The patch posted in http://sources.redhat.com/ml/cygwin/20

Re: rcs 5.7 truncated one of my files

H. I've removed cygwin from my system, and reinstalled it, and the problem seems to be gone. (I no longer have a problem with that particular file, and I have not exercised rcs beyond that.) I mentioned that I'd updated my cygwin recently. That update entailed downloading

Re: rcs 5.7 truncated one of my files

At 06:09 AM 11/23/2005, Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Max Bowsher on 11/22/2005 4:14 PM: > > RCS has not been updated in years. Could it be that RCS is still using 32-bit offsets because it has not been recompiled against newer cygwin head

Re: rcs 5.7 truncated one of my files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Max Bowsher on 11/22/2005 4:14 PM: > > RCS has not been updated in years. Could it be that RCS is still using 32-bit offsets because it has not been recompiled against newer cygwin headers to turn on 64-bit offsets? You can figur

Re: rcs 5.7 truncated one of my files

d to check in and then check out the second version again, > and the same truncation occurred as before. > > Between the initial revision and the time the problem occurred I updated > cygwin at least once, but I don't know whether rcs was updated at that > time. RCS has not been

rcs 5.7 truncated one of my files

tween the initial revision and the time the problem occurred I updated cygwin at least once, but I don't know whether rcs was updated at that time. I've checked one other file and it works fine. Richard Kandarian http://www.lanl.gov/cgi-bin/fonelink.pl/085598 Any opinions stated in t

RCS version 5.7 unable to lock files over network with Cygwin 1.5.11-1

Hi I upgraded to cygwin 1.5.11-1 recently and now I cannot lock files using RCS. Under 1.5.10-3 I didn't have any problems. The source is kept on an SCO server. When I need to make changes to a file I simply issue co -l file.c Under 1.5.11-1 when I try to lock a file I get the foll

Re: Options for Source Code Control: RCS v. SCCS v. CVS

--- Robert Collins wrote: > On Sun, 2004-07-11 at 03:09, Richard Heintze wrote: > > I need some help understanding how RCS works. I > typed > > "info RCS" and felt confused. > > Not surprisingly. RCS doesn't model what any modern > revision control >

Re: Options for Source Code Control: RCS v. SCCS v. CVS

Robert Collins schrieb: On Sun, 2004-07-11 at 03:09, Richard Heintze wrote: I need some help understanding how RCS works. I typed "info RCS" and felt confused. Not surprisingly. RCS doesn't model what any modern revision control system does. ?? For single developers (and e

Re: Options for Source Code Control: RCS v. SCCS v. CVS

On Sun, 2004-07-11 at 03:09, Richard Heintze wrote: > I need some help understanding how RCS works. I typed > "info RCS" and felt confused. Not surprisingly. RCS doesn't model what any modern revision control system does. > Is RCS like CVS in the sense that one runs a

Re: Options for Source Code Control: RCS v. SCCS v. CVS

Richard Heintze wrote: > I need some help understanding how RCS works. I typed > "info RCS" and felt confused. RCS more-or-less dead. I don't think it's seen a new release in years. > Does cygwin include the CVS windows service? If so, > how do I start it up? On

Re: Options for Source Code Control: RCS v. SCCS v. CVS

On Sat, 10 Jul 2004, Richard Heintze wrote: > I need some help understanding how RCS works. I typed > "info RCS" and felt confused. > > Is RCS like CVS in the sense that one runs a un*x > deamon or windows service on a remote node and legions > of programmers u

Options for Source Code Control: RCS v. SCCS v. CVS

I need some help understanding how RCS works. I typed "info RCS" and felt confused. Is RCS like CVS in the sense that one runs a un*x deamon or windows service on a remote node and legions of programmers use a client implemented with sockets or pipes. If so, (1) how do I start the

Observation - ntemacs + rcs + cygwin note (lowercase+uppercase userid workaround)

the native gui. I have a cygwin wrapper that does "cygpath -w" to my cygwin path names, and then passes the arg list to ntemacs. I found that on some machines, ntemacs+rcs would behave very strangely. I would be asked to steal the lock from "willisma" -- my userid. It worked fi

Re: rcs ci and co hang

Michael, On Fri, 7 Feb 2003, Michael Drumheller wrote: > I just tried running strace, and apparently I'm too much of > a rookie at it, because when I killed it it seemed to leave > a file under my RCS directory called _0002016, which seems > to be impossible for me to remove by

Re: rcs ci and co hang

> I just tried running strace, and apparently I'm too much of > a rookie at it, because when I killed it it seemed to leave > a file under my RCS directory called _0002016, which seems > to be impossible for me to remove by any means. That is a > little worrisome. Look a

Re: rcs ci and co hang

and he replied > "No I gave up on this >and subsequently on cygwin." > Bummer. Has anything changed on this? > Thanks, > MD Where abouts does rcs c{i,o} hang? You could strace a running/hanging c{i,o} which may help finding the glitch. Or even better run in under gd

rcs ci and co hang

I am running into the same problem that Mr. Tolkin encountered (ci and co hang on cywin). His original description is http://www.cygwin.com/ml/cygwin/2000-06/msg00018.html. I asked him if he ever found a fix (I was unable to find one anywhere on the cygwin mailing lists) and he replied "No I gav

Re: RCS and absolute file parameter

On Wed, May 15, 2002 at 09:03:58AM +, Davide Montesin wrote: >Hi, > >I have installed cygwin on my >Windows machine. >I use rcs. I have found >a problem. >Some time I will use rcs with >absolute parameter in windows format >like: > >ci -d -u -x,v c:\temp\a.t

RCS and absolute file parameter

Hi, I have installed cygwin on my Windows machine. I use rcs. I have found a problem. Some time I will use rcs with absolute parameter in windows format like: ci -d -u -x,v c:\temp\a.txt c:\temp\RCS\a.txt,v but the command report an error: file RCS/c:\temp\a.txt not found. The problem is

RE: RCS 5.7 and 5.7-2: Patch for potential solution to CR/LF problems

preserve the end-of-line style, so checking out previous versions would yield the correct text, but with the wrong line endings. I have created new patches, also found on http://pages.sbcglobal.net/dferreyra/ to fix these problems. The patch-rcs-5.7-for-cygwin-2.diff patch is for the RCS source from the

Re: RCS 5.7 and 5.7-2: Patch for potential solution to CR/LF problems

Christopher Faylor wrote: > > On Fri, Apr 12, 2002 at 05:17:59PM -0700, Dean Ferreyra wrote: > >I created patches for RCS to take care of its CR/LF problems. I have > >placed them here, http://pages.sbcglobal.net/dferreyra/, since I could > >not tell if attachments t

Re: RCS 5.7 and 5.7-2: Patch for potential solution to CR/LF problems

On Fri, Apr 12, 2002 at 05:17:59PM -0700, Dean Ferreyra wrote: >I created patches for RCS to take care of its CR/LF problems. I have >placed them here, http://pages.sbcglobal.net/dferreyra/, since I could >not tell if attachments to this list are accepted. The RCS maintainer for Cygwin

RCS 5.7 and 5.7-2: Patch for potential solution to CR/LF problems

Hello, I created patches for RCS to take care of its CR/LF problems. I have placed them here, http://pages.sbcglobal.net/dferreyra/, since I could not tell if attachments to this list are accepted. The patch-rcs-5.7-for-cygwin.diff patch is for the RCS source from the official RCS home page

Re: rcs 5.7-2 (1) on cygwin

"Dr. Ing. Dieter Jurzitza" schrieb: > > Dear Mr. Tolj, > today I installed and tested the version of rcs - 5.7-2 - you have been setting > up for the usage with cygwin. > Unfortunately I always get the following message: (NT 4.0 / SP 6) > > ci: RCS/.emacs,v: Permi

  1   2   >