[BLU/Officers] source control on cheyenne

[abreauj at gmail.com (John Abreau)]

How  do I do that? "git diff blu.org" outputs nothing, and when I tried
"git help diff", I didn't find any helpful clues.

With rcsdiff, I could do "rcsdiff -r1.44 -r1.43 blu.org" to compare revisions.



On Fri, Sep 23, 2011 at 8:56 AM, Jerry Feldman <gaf at blu.org> wrote:
> Quite a while ago I replaced RCS with git on cheyenne on those
> directories where we had been using rcs. There is really no problem I
> have with rcs except that it is no longer in favor.
> Git maintains its changes in the ./.git directory
> Unlike RCS you do not have to check anything out unless you are creating
> a new branch or retrieving an old file.
> To check a file in:
> git commit -m"comment" <file name[s]>
> or for all files.
> git commit -am"comment"
>
> Other useful git commands
> git status # lists what files are not committed or any files in the
> directory that have not been added to the repo
> git diff <filename>
> git add <file name[s]> # adds a file, but does not commit.
>
> There are other commands, but these are the ones you will use most often.
> The big difference is that you never need to checkout and lock a file.
>
> --
> Jerry Feldman <gaf at blu.org>
> Boston Linux and Unix
> PGP key id:3BC1EB90
> PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 ?C0AF 7CEA 30FC 3BC1 EB90
>
> _______________________________________________
> Officers mailing list
> Officers at blu.org
> http://lists.blu.org/mailman/listinfo/officers
>



-- 
John Abreau / Executive Director, Boston Linux & Unix
GnuPG KeyID: 0xD5C7B5D9 / Email: abreauj at gmail.com
GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99