[pygr-notify] [pygr commit] r99 - wiki

codesite-noreply at google.com codesite-noreply at google.com
Mon Aug 25 17:43:46 PDT 2008


Author: cjlee112
Date: Mon Aug 25 17:43:19 2008
New Revision: 99

Modified:
    wiki/UsingGit.wiki

Log:
Edited wiki page through web user interface.

Modified: wiki/UsingGit.wiki
==============================================================================
--- wiki/UsingGit.wiki	(original)
+++ wiki/UsingGit.wiki	Mon Aug 25 17:43:19 2008
@@ -89,6 +89,23 @@
  Here we switch to the branch we want to change (in case we're not already  
on that branch).
  Then you specify the commit you want to apply via its SHA1 hash code, or  
in this case just its first few digits.

+=== Abandon any uncommitted changes, returning to last commit ===
+{{{
+git reset --hard HEAD
+}}}
+If you want to get rid of the last two *commits* as well:
+{{{
+git reset --hard HEAD-2
+}}}
+Don't do the latter if you have already exposed those commits to other  
people!!!
+
+=== Push updates from one machine to another ===
+Say you have a test machine that currently has just the master branch  
cloned from the public repository.  Now suppose you have made a bunch of  
new changes on a new branch called "seqdb_refactor" on your main  
development machine, and want to test these changes on the test machine.   
Instead of having to push the new changes to the public repository, and  
then pull them to the test machine, you can push them directly to the test  
machine over ssh.  From your development machine, in your development  
repository:
+{{{
+git push 'ssh://my.test.machine.address/~/projects/pygr/.git'  
seqdb_refactor
+}}}
+If the test machine repository doesn't have the seqdb_refactor branch, it  
will be created automatically.
+
  === Generate patch output for emailing me your changes ===
  {{{
  git format patch master >my_patches.txt



More information about the pygr-notify mailing list