Replace several stale references to the stgit git repo and mailing list.
Signed-off-by: Peter Grayson <[email protected]>
---
Documentation/SubmittingPatches | 8 ++++----
Documentation/tutorial.txt | 4 ++--
README | 4 ++--
examples/gitconfig | 1 +
4 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index ec2d3d65..79a2674f 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -37,7 +37,7 @@ Checklist (and a short version for the impatient):
documentation should be updated as well.
- If your name is not writable in ASCII, make sure that
you send off a message in the correct encoding.
- - Send the patch to the list ([email protected]) and the
+ - Send the patch to the list ([email protected]) and the
maintainer ([email protected]) if (and only if) the
patch is ready for inclusion.
@@ -81,8 +81,8 @@ Long version:
3. Sending your patches.
- StGit patches should be sent to the Git mailing list
- ([email protected]), and preferably CCed to the StGit maintainer
+ StGit patches should be sent to the StGit mailing list
+ ([email protected]), and preferably CCed to the StGit maintainer
([email protected]). The recipients need to be able to read
and comment on the changes you are submitting. It is important for
a developer to be able to "quote" your changes, using standard
@@ -225,7 +225,7 @@ One test you could do yourself if your MUA is set
up correctly is:
* Try to apply to the tip of the "master" branch from the
public repository:
- $ git fetch http://homepage.ntlworld.com/cmarinas/stgit.git
master:test-apply
+ $ git fetch http://repo.or.cz/stgit.git master:test-apply
$ git checkout test-apply
$ git reset --hard
$ stg init
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
index 9dee5d83..d9c88173 100644
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -211,7 +211,7 @@ Normally, when you pop a patch, change something,
and then later push
it again, StGit sorts out everything for you automatically. For
example, let's create two patches that modify different files:
- $ stg clone http://homepage.ntlworld.com/cmarinas/stgit.git stgit
+ $ stg clone http://repo.or.cz/stgit.git stgit
$ cd stgit
$ stg new first --message 'First patch'
$ echo '- Do something' >> TODO
@@ -532,7 +532,7 @@ history at the time, your stack base will grow
ever more out of date.
When you clone a repository,
- $ stg clone http://homepage.ntlworld.com/cmarinas/stgit.git stgit
+ $ stg clone http://repo.or.cz/stgit.git stgit
you initially get one local branch, +master+. You also get a number of
'remote' branches, one for each branch in the repository you cloned.
diff --git a/README b/README
index 311c08dc..cbe93b7c 100644
--- a/README
+++ b/README
@@ -9,7 +9,7 @@ previously initialised Git repository (unless it is
cloned using StGit
directly). For standard SCM operations, use plain Git commands.
For the latest version see http://www.procode.org/stgit/
-For a tutorial see http://wiki.procode.org/cgi-bin/wiki.cgi/StGit_Tutorial
+For a tutorial see http://www.procode.org/stgit/doc/tutorial.html
-Bugs or feature requests should be sent to the [email protected]
+Bugs or feature requests should be sent to the [email protected]
mailing list or the StGit project page - http://gna.org/projects/stgit/
diff --git a/examples/gitconfig b/examples/gitconfig
index 48a42468..301c84b4 100644
--- a/examples/gitconfig
+++ b/examples/gitconfig
@@ -92,6 +92,7 @@
[mail "alias"]
# E-mail aliases used with the 'mail' command
git = [email protected]
+ stgit = [email protected]
[stgit "color"]
# Specify output colors for series commands
--
2.12.0
_______________________________________________
stgit-users mailing list
[email protected]
https://mail.gna.org/listinfo/stgit-users
