commit: 470ee34f9ad87845f24fe4fe1bcd4d6b3f1be5e3
Author: Mike Pagano <mpagano <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 30 12:55:34 2014 +0000
Commit: Mike Pagano <mpagano <AT> gentoo <DOT> org>
CommitDate: Mon Jun 30 12:55:34 2014 +0000
URL:
http://git.overlays.gentoo.org/gitweb/?p=proj/linux-patches.git;a=commit;h=470ee34f
Update documentation scripts
---
repo-doc/00_intro | 13 ++++++-------
repo-doc/10_scripts | 35 +++++++++++++++++++++++------------
repo-doc/20_release-howto | 6 +-----
3 files changed, 30 insertions(+), 24 deletions(-)
diff --git a/repo-doc/00_intro b/repo-doc/00_intro
index 9153a1b..895a117 100644
--- a/repo-doc/00_intro
+++ b/repo-doc/00_intro
@@ -1,16 +1,17 @@
Repository layout for linux-patches/genpatches-2.6
==================================================
-trunk: This contains the 'branches' which we are actively developing.
- Each branch is held in its own directory, e.g. "2.6.11" and "2.6.12-pre"
- -pre versions represent development patchsets for latest -rc kernels.
+trunk: Trunk only contains the 0000_README file and one generic patch
+
+branch: For each kernel branch we support we have a correspding branch in
+ our repo. We have branches at the minor level. e.g.
3.14,3.15,etc
tags: Whenever we snapshot a branch and release it in tarballs, we tag it in
the repository, as the full kernel name plus our own release version,
e.g. 2.6.11-9
historical: When we stop actively developing a branch, we move the branch as-is
- to here.
+ to here. TODO
Checking out the working repository
===================================
@@ -18,7 +19,5 @@ Checking out the working repository
Most of the time, you will only need to work under trunk - there is no point
checking out all the tagged and historical branches.
-# svn co \
-
svn+ssh://[email protected]/var/svnroot/linux-patches/genpatches-2.6/trunk
genpatches
-
+# git clone git+ssh://[email protected]/proj/linux-patches.git
diff --git a/repo-doc/10_scripts b/repo-doc/10_scripts
index 823ddf6..e73eb47 100644
--- a/repo-doc/10_scripts
+++ b/repo-doc/10_scripts
@@ -26,33 +26,38 @@ variables.
Here's a sample config:
--- start ~/.genpatchesrc -----------------------------------------------------
-# Your username for Gentoo SVN
-USERNAME="dsd"
+# Your username for Gentoo Git
+USERNAME="mpagano"
-# The path to the directory where you have checked out trunk
-LOCAL_PATCHES_TRUNK="/home/dsd/projects/gentoo/genpatches"
+# The path to the directory where you have cloned the repo
+LOCAL_PATCHES_TRUNK="/home/mike/gentoo/linux-patches"
+
+#temporary directory
+LOCAL_TMP="/tmp"
# Remote repository configuration
-REMOTE_BASE="svn+ssh://${USERNAME}@svn.gentoo.org/var/svnroot/linux-patches"
-REMOTE_TRUNK="${REMOTE_BASE}/genpatches-2.6/trunk"
-REMOTE_TAGS="${REMOTE_BASE}/genpatches-2.6/tags"
+REMOTE_BASE="git+ssh://[email protected]/proj/linux-patches.git"
TARBALL_BASENAME="genpatches"
KERNEL_NAME="genpatches"
-WE_WANT="base extras experimental"
-DO_WEBSITE="yes"
+DO_WEBSITE="no"
DO_EMAIL_ANNOUNCEMENT="yes"
# Website/email stuff
-WEB_LOCAL="/home/dsd/projects/gentoo/genpatches-misc/web"
-WEB_GENPATCHES_BASE="dev.gentoo.org:/home/dsd/public_html/genpatches"
-SENDMAIL="ssh dsd@zog /usr/sbin/sendmail"
+WEB_LOCAL="/home/mike/gentoo/linux-patches-misc/web"
+WEB_GENPATCHES_BASE="dev.gentoo.org:/home/mpagano/public_html/genpatches"
+SENDMAIL="ssh [email protected] /usr/sbin/sendmail"
+
+WE_WANT="base extras experimental"
+
--- end ~/.genpatchesrc -------------------------------------------------------
gppatch
=======
+TODO - not yet converted go support git migration
+
Applies a single genpatches patch to a kernel source tree in the current
directory.
@@ -71,6 +76,8 @@ To dry-run a patch you can do:
gpmultipatch
============
+TODO - not yet converted go support git migration
+
Applies a trunk genpatches branch to a kernel source tree in the current
directory.
@@ -112,6 +119,8 @@ Post-commit hooks
gpcreatebranch
==============
+TODO - not yet converted go support git migration
+
Copy one branch to another under trunk.
Example: This will create a 2.6.13-pre branch from the 2.6.12 branch
@@ -121,6 +130,8 @@ Example: This will create a 2.6.13-pre branch from the
2.6.12 branch
gpmvhistorical
==============
+TODO - not yet converted go support git migration
+
Move a trunk branch into historical
Example: Move 2.6.11 into historical:
diff --git a/repo-doc/20_release-howto b/repo-doc/20_release-howto
index 7bea709..f28cfd7 100644
--- a/repo-doc/20_release-howto
+++ b/repo-doc/20_release-howto
@@ -13,10 +13,6 @@ the last 2.6.11 release. If there was no previous release,
it will use
"2.6.11-1", but if it (e.g.) found the previous release to be "2.6.11-3" then
it will use a new version of "2.6.11-4".
-It will then copy the 2.6.11 branch into tags as the new version number deduced
-above.
-
It will then generate tarballs of the branch, named with the same version tag,
placed into /tmp. These tarballs will then be uploaded to distfiles-local on
-toucan.
-
+woodpecker.
