Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
Essentially, 'git status -s' would be the appropriate one. If it returns anything to stdout, then you can either parse the result or just note that the repository is unclean. Certainly setting up aliases are good, but if you are accessing commands from a script that is being used by others, it is best to use the full path. The other thing is for me to set up a script to both do a commit and set up a tag. That is probably a 10 - 20 line bash script. On 10/27/2011 11:36 AM, Doug wrote: >> One additional related question. Suppose the running code is >> uncommitted, how easy is it to determine if the code has been committed. > git status??? > > I use that command so often, I alias it to gs. > > alias ga='git add' > alias gs='git status' > alias gl='git pull' > alias gp='git push' > alias gd='git diff' > alias gc='git commit -v' > alias gca='git commit -v -a' > alias gb='git branch' > aliases:alias gba='git branch -a' > alias glog='git log' > alias gre='git rebase' # sync up branches > alias gco='git checkout' # revert file, change branch -- 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
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |