Hints on using GIT and stgit - Revision history

Glenn: /* Overview: stgit and git */ +link

2009-07-19T12:07:50Z

‎Overview: stgit and git: +link

2009-07-19T11:10:01Z

catchg

2009-03-31T16:52:52Z

The quotes are useful in case of names with more of one word. I got bit by this when using the stg-send-email script.

2009-02-25T03:23:55Z

Fix.

2009-02-25T03:22:39Z

‎Sending a set of patches

2009-02-25T03:10:30Z

‎Sending a set of patches

2009-02-25T03:09:57Z

‎Sending a set of patches

2009-02-25T03:08:42Z

‎Sending a set of patches

2009-02-25T03:06:48Z

‎Useful scripts - sending patchsets via email / I meant gmail

2009-02-12T20:02:57Z

‎Making your tree public on git.openmoko.org

@@ Line 1: / Line 1: @@
 =Overview: stgit and git=
-Linus Torvalds invented git and uses it heavily in Linux development, most people would take that as an impressive suggestion it might be useful in kernel and similar development work.
+Linus Torvalds invented [http://en.wikipedia.org/wiki/Git_%28software%29 git] and uses it heavily in Linux development, most people would take that as an impressive suggestion it might be useful in kernel and similar development work.
 * '''git''' is a lightweight distributed revision control system.  In practical terms, it adds a ./.git directory in the top level of your project, git stores everything in there about your project including all the revisions.  The commands all start "git <something>".  ''Nice feature: if you create tarball of your project directory, you will also capture all your project history as it will archive ./.git''

@@ Line 280: / Line 280: @@
 {{Languages|Hints_on_using_GIT_and_stgit}}
-[[Category:System Developers]]
+[[Category:Developer resources]]
-[[Category:Application Developer]]

@@ Line 15: / Line 15: @@
 You can optionally edit your ~/.bashrc to define some environment variables to control your commit identity for git
-* export GIT_AUTHOR_NAME=yourhandle
+* export GIT_AUTHOR_NAME="yourhandle"
-* export GIT_COMMITTER_NAME=yourhandle
+* export GIT_COMMITTER_NAME="yourhandle"
 * export GIT_AUTHOR_EMAIL="your@email"
 * export GIT_COMMITTER_EMAIL="your@email"

@@ Line 277: / Line 277: @@
   # thus I don't care much. A better way to do this?
   stg mail $OPT -a --to $TO --smtp-server smtp.gmail.com:587 -u $GMAIL_USER_NAME -p $PASS -T $OPT
 [[Category:System Developers]]
 [[Category:Application Developer]]

@@ Line 267: / Line 267: @@
   TO=new_kernel_hacker@gmail.com # Send these first for yourself and check!
   echo "pass:"
   read -s PASS

@@ Line 275: / Line 275: @@
   GMAIL_USER_NAME=new_kernel_hacker
   # this will disclose your password to ps! I am the only user in my machine
   # thus I don't care much. A better way to do this?

@@ Line 260: / Line 260: @@
 ==Sending a set of patches==
-Send a patch using a gmail account. You will find a way to make this work for you with another provider.
+Send a patch using a gmail account. You have to find a way to make this work for you with another provider.
-−
   OPT=

@@ Line 219: / Line 219: @@
 =Making your tree public on git.openmoko.org=
-# Send your ssh key to Gismo.  He will add it to the git user authorized_keys, so you can ssh in
+# go to http://admin-trac.openmoko.org and open a ticket
-# '''ssh git@git.openmoko.org'''
+# attach your public key to the ticket and also add some descriptions.
-# '''cd /var/cache/git'''
-# '''./ADD_NEW_REPO <your-project-name>''' -- without the .git on the end
-# in your project directory, execute the suggested git push command shown by the ADD_NEW_REPO script
-# '''vi <your-project-name>.git/description''' -- change to a few words describing your project
-# You can immediately see your tree on http://git.openmoko.org/ and browse it
-−
-Keep a copy of the git push command, you can use it without the --all to update the remote git repo with changes to your local git
-−
-If something goes wrong, you can fully delete your project on there with
-−
-'''rm -rf /var/cache/git/<your-project-name>.git'''
-−
-and start over from step 3.
-−
-You can backup your remote repo either on the git.openmoko.org box by using:
-−
-'''tar czf /home/git/<project>-backup.tar.gz /var/cache/git/<project>.git'''
-−
-or remotely by something like:
-−
-'''rsync -avz --delete git@git.openmoko.org:/var/cache/git/<project>.git <project>-backup'''
 =Useful scripts=