Boston Linux & UNIX was originally founded in 1994 as part of The Boston Computer Society. We meet on the third Wednesday of each month, online, via Jitsi Meet.

BLU Officers list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[BLU/Officers] source control on cheyenne



On 09/23/2011 08:56 AM, Jerry Feldman 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.

OK, looked at git, and it works just like Mercurial, which is what we
use at work.  No problems there.

But what's in source control?

Where is the repo?






BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org