Changes between Version 6 and Version 7 of GitMigrationProposal

Timestamp:

03/15/09 06:04:33 (4 years ago)

Author:

cdavid

Comment:

--

GitMigrationProposal

@@ -105 +105 @@
 }}}
 
-== Scenario 1 ==
+== Scenario 1: getting the numpy source code ==
 
 Getting the sources from the NumPy repository, just to look at the sources, or to build from last version instead of released:
@@ -113 +113 @@
 }}}
 
+Do NOT use checkout - checkout has a different meaning than in svn. Clone is what you want.
+
 A tarball will also be made available on the scipy website, so that you don't need git at all in this scenario.
 
-== Scenario 2 ==
+== Scenario 2: prepare a simple patch ala svn, don't bother me with git ==
 
 I have found a bug, and I want to submit a patch. I want to do it like in svn, I don't care about git:
@@ -125 +127 @@
 git diff
 }}}
+
+Maybe: we could have a svn mirror of git ?
 
 == Scenario 3: reverting changes ==
@@ -149 +153 @@
 
 This will have the same semantics as svn revert.
+
+Q: I thought that git reset was the option to use ?
+
+No, don't use git reset. Git reset can be used to revert changes, but can be dangerous to use, as it can also remove *commits*, not just changes. git reset is only useful for advanced usage of git. Use git stash or git co, not git reset.