Add RCS resources #6669
Add RCS resources #6669
Conversation
| ### RCS | ||
|
|
||
| * [RCS — A System for Version Control](https://www.cs.purdue.edu/homes/trinkle/RCShome/rcs.ps) - Walter F. Tichy (PS) | ||
| * [RCS Handbook](https://www.cs.purdue.edu/homes/trinkle/RCShome/contrib/odonavan/RCS_Book.tar.Z) - Brian O’Donovan |
There was a problem hiding this comment.
Should we accept compressed files?
There was a problem hiding this comment.
There are some link that redirect to a compressed files so I think we accept those.
Example:
Although a .pdf or something easier to view would be better than a tar.z archive containing .ps files.
There was a problem hiding this comment.
we should probably remove that zip.
we can't provide enough context on our list to link to tar files.
If the purdue people thought the book was important to share, they'd produce a pdf or something of it. If they don't think it's worthwhile, why should we link to it?
| @@ -2074,6 +2075,12 @@ That section got so big, we decided to split it into its own file, the [BY SUBJE | |||
| * [The Official Raspberry Pi Project Book 1 (2015)](https://magpi.raspberrypi.com/books/projects-1) (PDF) | |||
|
|
|||
|
|
|||
| ### RCS | |||
|
|
|||
| * [RCS — A System for Version Control](https://www.cs.purdue.edu/homes/trinkle/RCShome/rcs.ps) - Walter F. Tichy (PS) | |||
There was a problem hiding this comment.
Fixing file format notes
| * [RCS — A System for Version Control](https://www.cs.purdue.edu/homes/trinkle/RCShome/rcs.ps) - Walter F. Tichy (PS) | |
| * [RCS — A System for Version Control](https://www.cs.purdue.edu/homes/trinkle/RCShome/rcs.ps) - Walter F. Tichy (PostScript) |
Are there any other format easier readable like PDF, ePub...?
There was a problem hiding this comment.
@davorpa
GNU has a PDF version: https://www.gnu.org/software/rcs/tichy-paper.pdf
FreeBSD too: https://docs.freebsd.org/44doc/psd/13.rcs/paper.pdf
There was a problem hiding this comment.
I think that it would be better to replace the .ps link with the GNU link
There was a problem hiding this comment.
We don't list articles. There are millions of those. If we did, we would link to the gnu pdf.
There was a problem hiding this comment.
@davorpa GNU has a PDF version: gnu.org/software/rcs/tichy-paper.pdf FreeBSD too: docs.freebsd.org/44doc/psd/13.rcs/paper.pdf
I agree with Luigi and Eric attending to contrib guidelines, using PDF or ePUB, and even use a gnu.org as target domain. Meanwhile... I'd opt to fix file format notes with the proposed name
|
If is a version control system, we should remember include it later in the reorganization proposed via #5526 |
There was a problem hiding this comment.
It's not our goal to document 40 year old software "primarily of historical interest". Wikipedia has a good article on it. RCS is not worth a section of its own as far as I can tell. If there were a book on it we would include it in our CVS section, if we even had a CVS section. or our "history of software" section if we had that.
Also RCS is today too obscure an acronym for us to use as a heading.
Thank you for the suggestion; it is appreciated even if not accepted!
| @@ -2074,6 +2075,12 @@ That section got so big, we decided to split it into its own file, the [BY SUBJE | |||
| * [The Official Raspberry Pi Project Book 1 (2015)](https://magpi.raspberrypi.com/books/projects-1) (PDF) | |||
|
|
|||
|
|
|||
| ### RCS | |||
|
|
|||
| * [RCS — A System for Version Control](https://www.cs.purdue.edu/homes/trinkle/RCShome/rcs.ps) - Walter F. Tichy (PS) | |||
There was a problem hiding this comment.
We don't list articles. There are millions of those. If we did, we would link to the gnu pdf.
| ### RCS | ||
|
|
||
| * [RCS — A System for Version Control](https://www.cs.purdue.edu/homes/trinkle/RCShome/rcs.ps) - Walter F. Tichy (PS) | ||
| * [RCS Handbook](https://www.cs.purdue.edu/homes/trinkle/RCShome/contrib/odonavan/RCS_Book.tar.Z) - Brian O’Donovan |
There was a problem hiding this comment.
we should probably remove that zip.
we can't provide enough context on our list to link to tar files.
If the purdue people thought the book was important to share, they'd produce a pdf or something of it. If they don't think it's worthwhile, why should we link to it?
|
What do you think, @cwfoo ? (You were tied for sixth for most F-P-B contributions in 2021!) |
I occasionally use RCS myself, but I completely understand that RCS is widely considered obsolete these days (it was long ago removed from the base system of the BSDs). In any case, the "books" submitted in this pull request can easily be found through the most obvious webpages:
This pull request can now be closed. This pull request can be revisited in the future when there are more appropriate sections in the book lists.
This is most surprising. 😆 Only 7 commits! |
What does this PR do?
Add Revision Control System (RCS) resources.
For resources
Description
Add two resources:
Why is this valuable (or not)?
RCS Handbook is particularly valuable because it goes far beyond the man pages and the short tutorials found on various websites. For example, the book teaches about branching, merging, and managing software projects.
How do we know it's really free?
These texts are made available on the Purdue RCS Homepage.
For book lists, is it a book? For course lists, is it a course? etc.
One paper and one book.
Checklist: