On Tue, Apr 21, 2009 at 06:23:55AM +1000, Paul Gear wrote: > Tom Eastep wrote: > > As I announced earlier, Shorewall is transitioning from SVN to Git for SCM. > > > > The first step was to create a Git repository from the SVN repository at > > Sourceforge. > > > > ... > > Rather than fight these problems, I'm going to simply stop updating > > trunk in the SVN repository at Sourceforge. All trunk development going > > forward will only be pushed to the Git repository. > > Can anyone recommend a 1-minute crash course/survival kit for us > git-ignorant plebs? Git is otherwise very low on my priority list.
To grab a copy of the tree initially: git clone giturl To update it later: git pull (from inside the git tree) Handy things: git log - shows changes git log filename - shows changes that involved that file git log -Sfoobar filename - shows changes that involved that file and the keyword foobar git checkout v2.4 - switch the state of the tree to v2.4 tag git checkout master - switch the state of the tree to the head git show 1234567890abcdef - show commit 1234567890abcdef git diff v2.4 - show diff between current and v2.4 tag. git add - Add file to tree git commit - Commit changes to tracked files as a changeset. There are lots of useful things too like git mv (rename), git tag (manage tags) git revert (revert a changeset), etc. -- Len Sorensen ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
