On May 21, Carl Eastlund wrote:
> deleting it and running 'git pull'; the equivalent works in svn. It
> didn't work, and he ran 'git commit -a' and 'git push' without
> checking 'git status' to see what state he was actually
> committing/pushing.
To repeat some points from my text (from the "staging area" section):
* Avoid the `-a' flag -- despite what you see on random web pages,
using `-a' is a bad idea.
* Always specify a path to "git commit" -- this is a much more proper
way to avoid git's "staging area" concept. (Also, look through the
text for "git-ci" -- I wrote that quick script as a more svn-like
replacement for "svn commit".)
* Avoid using the `-m' flag, until you're more comfortable with git.
Not using `-m' means that you get an editor to write your commit
message, and that editor will have a detailed description of what
changes you're committing, and what changes (if any) you're not
comitting. This text is what you see with `git status' too.
* Don't push out all commits to the server immediately. If you let
them sit around your directory for a while, you'll have more chances
to look at them and fix any problems you might have committed before
you push them out.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________________________________
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-dev
