2 ms·

I know that, but the main thing I do not like about git is the source is not updated with version tags like in RCS. So when I dumped github I decided to move b

by jmclnx 3y ago

I know that, but the main thing I do not like about git is the source is not updated with version tags like in RCS. So when I dumped github I decided to move back to RCS because of $Id$ If git had something like that I would have stuck with it.

eropple 3y ago
I've never used RCS; what do you feel like you're getting from that? My editor can tell me committed-on if I want it to, so it's a bit of a head-scratcher for me.
- jmclnx 3y ago
  Really just 2 things: * Tags in the binary which can be listed using ident(1) * If I have a object checked out, no one can check in their changes without talking to me. Most other SC deals with this automatically, but I am old school :) * works nice with emacs, but on OpenBSD the emacs interface is broken, you need to install GNU RCS for OpenBSD :( One thing I really like about git is gpg signing on commit, but on the BSDs pinentry* does not prompt when used from inside emacs, so signing fails when using gpg
  - RHSeeger 3y ago
    > If I have a object checked out, no one can check in their changes without talking to me. The inability to lock checkouts is one of the things that a co-worker of mine fought tooth and nail about when we moved from RCS to CVS.
    - jmclnx 3y ago
      Sounds like an argument I had too :)
loloquwowndueo 3y ago
https://stackoverflow.com/questions/31769003/git-can-i-get-the-equivalent-of-an-rcs-id-string#31769199 https://stackoverflow.com/questions/31769003/git-can-i-get-t...
microtherion 3y ago
Others have pointed out that you can retrofit a similar or even more powerful mechanism into git. Alternatively, CVS and SVN have RCS-style keyword expansion built in. Either of these is an obvious improvement over RCS, so I don't think there are any good reasons not to upgrade.