[debian-edu-commits] [Debian Wiki] Update of "DebianEdu/HowTo/Git" by HolgerLevsen
Debian Wiki
wiki at debian.org
Tue Jun 12 15:16:36 BST 2018
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.
The "DebianEdu/HowTo/Git" page has been changed by HolgerLevsen:
https://wiki.debian.org/DebianEdu/HowTo/Git?action=diff&rev1=19&rev2=20
Comment:
move subversion down
= Debian Edu Git =
Beginning with Debian Edu wheezy (7.0) Debian Edu development has moved from using SVN to using Git (both on Alioth); since 2018-05-30, the Debian Edu Git repositories are hosted on https://salsa.debian.org, Alioth has been shut down 2018-06-01.
-
- == SVN-2-Git Migration Status ==
-
- The migration status of the Debian Edu project files from SVN to Git to Salsa is documented [[DebianEdu/HowTo/Git/SVN2GitMigrationStatus|here]]. Please note the different locations ''debian-edu'', ''debian-edu/upstream'' and ''debian-edu-pkg-team'' on Salsa.
-
- == SVN vs. Git ==
-
- For those that are not familiar with Git there are some major differences in a Git-based workflow compared to an SVN-based workflow.
-
- * Git commits are local first, with Git you can work offline.
- * Git pushes (to a central location) are similar to SVN commits. However, Git pushes can contain several local commits whereas an SVN commit is just a single commit.
- * With Git we have loads of little repositories (one per Debian package), with SVN we just had a huge directory tree.
- * With Git tags and branches are much nicer and completely different from the handling in SVN.
- * Git does not know about folders. Git only know files. If you intend to place a(n empty) folder somewhere inside a Git repos you have to create an empty {{{.placeholder}}} file in that folder.
== Setting up a Debian Edu related Git project ==
@@ -56, +42 @@
Again: refer to this location: http://wiki.debian.org/PackagingWithGit
+
+ == Before Git we used Subversion ==
+
+ === SVN-2-Git Migration Status ===
+
+ The migration status of the Debian Edu project files from SVN to Git to Salsa is documented [[DebianEdu/HowTo/Git/SVN2GitMigrationStatus|here]]. Please note the different locations ''debian-edu'', ''debian-edu/upstream'' and ''debian-edu-pkg-team'' on Salsa.
+
+ === SVN vs. Git ===
+
+ For those that are not familiar with Git there are some major differences in a Git-based workflow compared to an SVN-based workflow.
+
+ * Git commits are local first, with Git you can work offline.
+ * Git pushes (to a central location) are similar to SVN commits. However, Git pushes can contain several local commits whereas an SVN commit is just a single commit.
+ * With Git we have loads of little repositories (one per Debian package), with SVN we just had a huge directory tree.
+ * With Git tags and branches are much nicer and completely different from the handling in SVN.
+ * Git does not know about folders. Git only know files. If you intend to place a(n empty) folder somewhere inside a Git repos you have to create an empty {{{.placeholder}}} file in that folder.
+
+
+
----
CategoryGit
More information about the debian-edu-commits
mailing list