[NBP web-reskin] (3) More ID's needed

[Didomenico, Steven]

Thanks Edit 

-----Original Message-----
From: web-reskin-bounces at nbp.org [mailto:web-reskin-bounces at nbp.org] On
Behalf Of Edie Coletti
Sent: Monday, August 03, 2009 9:53 AM
To: 'Discussions regarding the 2009 UI reskin of nbp.org';
ethan at endpoint.com
Cc: Patel, Komal; Prabhakar, V
Subject: RE: [NBP web-reskin] (3) More ID's needed

Hi Steve:
In addition to camp26, you now have four additional camps
(camp28,camp29,camp30, camp31).  Here are the git commands that I use
most
during development.
git help [any command]
git status (status of working tree - what's changed & what' has/hasn't
been
committed)
git add [filename] (adds file name to index for later commits)
git commit (records changes to repository - all the files added to the
index)
git diff (difference between staged area and commits)
git pull -rebase (pulls anything new from commits in local repository)
git push --dry-run (test the push to local repository)
git push (push commits to local repository)

In a typical session I will:
1. git status
2. git pull -rebase (pull in anything new - sync up)
3. git push --dry-run. (Use when satisfied that the files that have been
edited or the new files added are ready to be pushed to the central
repository to share with other developers)
4. git push (Use if the dry run went without a hitch)

If you are using camp26 as the staging area, then you would only git
pull
for pull in the latest commits.

Thanks,
Edie 


_______________________________________________
Web-reskin mailing list
Web-reskin at nbp.org
http://www.nbp.org/mailman/listinfo/web-reskin