BLU Officers list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[BLU/Officers] source control on cheyenne
- Subject: [BLU/Officers] source control on cheyenne
- From: gaf at blu.org (Jerry Feldman)
- Date: Fri, 23 Sep 2011 11:22:11 -0400
- In-reply-to: <CAFv2jcYt+Xj+bhYKP6h3krLHx8DeVkzgN+h+8zvF8gpw2c3gxg@mail.gmail.com>
- References: <4E7C81EB.10106@blu.org> <CAFv2jcYt+Xj+bhYKP6h3krLHx8DeVkzgN+h+8zvF8gpw2c3gxg@mail.gmail.com>
I committed everything. You would need to compare the current version to a prior commit. http://book.git-scm.com/3_comparing_commits_-_git_diff.html git diff [options] [<commit>] [--] [<path>...] Git log will show you the commits. This will show all changes since the previous 2 commits. git diff 88f057dc4179138e7bd618e71c7849aa5c1dfcb9 -- blu.org Remember that git is now the preferred source control. While RCS worked, since you created cheyenne, you did not set up RCS, I set up git. On 09/23/2011 11:00 AM, John Abreau wrote: > 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 >> > > -- 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
- References:
- [BLU/Officers] source control on cheyenne
- From: gaf at blu.org (Jerry Feldman)
- [BLU/Officers] source control on cheyenne
- From: abreauj at gmail.com (John Abreau)
- [BLU/Officers] source control on cheyenne
- Prev by Date: [BLU/Officers] source control on cheyenne
- Next by Date: [BLU/Officers] Fwd: John Abreau, your August account statement is here
- Previous by thread: [BLU/Officers] source control on cheyenne
- Next by thread: [BLU/Officers] source control on cheyenne
- Index(es):