[BLU/Officers] source control on cheyenne

[jabr at blu.org (John Abreau)]

In this case, the DNS zone files.


On Fri, Sep 23, 2011 at 9:43 PM, David Kramer <david at thekramers.net> wrote:
> 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?
>
>
> _______________________________________________
> Officers mailing list
> Officers at blu.org
> http://lists.blu.org/mailman/listinfo/officers
>



-- 
John Abreau / Executive Director, Boston Linux & Unix
AIM abreauj / JABBER jabr at jabber.blu.org / YAHOO abreauj / SKYPE zusa_it_mgr
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99