Changeset - 0a5d6db00372
[Not reviewed]
0 4 0
Bradley Kuhn (bkuhn) - 9 years ago 2015-04-03 03:32:33
bkuhn@ebb.org
Gitorious Apocalypse: remove all gitorious URLs

The Gitorious URLs will disappear in the next few hours. The canonical
hosting location of this project is now on copyleft.org. Specific
gitorious URLs are generally replaced with k.copyleft.org, which is
copyleft.org's self-hosted Kallithea instance.
4 files changed with 42 insertions and 42 deletions:
0 comments (0 inline, 0 general)
CONTRIBUTING.md
Show inline comments
...
 
@@ -13,3 +13,3 @@ this Guide project.  However, many other contributors have given patches and
 
improvements to the text.  Review the
 
[commit log in the Git repository](https://gitorious.org/copyleft-org/tutorial/commits/master)
 
[commit log in the Git repository](https://k.copyleft.org/guide/changelog)
 
for more details on who has contributed to the project.
...
 
@@ -19,8 +19,9 @@ for more details on who has contributed to the project.
 
The Guide is maintained in a copylefted distributed version control system called
 
[Git](http://git-scm.com/).  Currently, the project utilizes the services of
 
a  Git hosting website called [Gitorious](https://gitorious.org). (The
 
software which runs Gitorious is, itself, copylefted, too.)
 
[Git](http://git-scm.com/).  Currently, the project collaboration site is an
 
instance of the [Kallithea code hosting software](https://kallithea-scm.org/)
 
hosted at [k.copyleft.org](https://k.copyleft.org/guide/).  (Kallithea itself
 
us under a copyleft license, too, namely GPLv3.)
 

	
 
Those who are comfortable with Gitorious can submit
 
[merge requests on copyleft.org's gitorious site](https://gitorious.org/copyleft-org/tutorial/merge_requests).
 
Those who are comfortable with using Kallithea can submit
 
[pull requests via the Kallithea interface](https://k.copyleft.org/guide/pull-request).
 
See the section "Merge Request and Patch Workflow" below for more information
...
 
@@ -113,3 +114,3 @@ procedures when doing so:
 

	
 
   [Commit 678e841079aa708f98fe948ec8cef672d9a4c3cc](https://gitorious.org/copyleft-org/tutorial/commit/678e841079aa708f98fe948ec8cef672d9a4c3cc)
 
   [Commit 678e841079aa708f98fe948ec8cef672d9a4c3cc](https://k.copyleft.org/guide/changeset/678e841079aa708f98fe948ec8cef672d9a4c3cc)
 
   contains an example of this specific procedure.
...
 
@@ -143,3 +144,3 @@ procedures when doing so:
 

	
 
   [Commit 07a02b0b1c6d3ac2af9ed21b2a563abcf44d3d0f](https://gitorious.org/copyleft-org/tutorial/commit/07a02b0b1c6d3ac2af9ed21b2a563abcf44d3d0f)
 
   [Commit 07a02b0b1c6d3ac2af9ed21b2a563abcf44d3d0f](https://k.copyleft.org/guide/changeset/07a02b0b1c6d3ac2af9ed21b2a563abcf44d3d0f)
 
   is an example of the process for the last two steps.
...
 
@@ -153,5 +154,5 @@ procedures when doing so:
 
Currently, the main location for work on this project is
 
[on Gitorious](https://gitorious.org/copyleft-org/tutorial), and active new
 
[on k.copyleft.org](https://k.copyleft.org/guide), and active new
 
development on the project happens on the
 
['next' branch](https://gitorious.org/copyleft-org/tutorial/source/next:)
 
['next' branch](https://k.copyleft.org/guide/changelog?branch=next)
 
(which is
...
 
@@ -163,6 +164,6 @@ infrastructure but still using Git, and third avoiding Git altogether.
 
Merge requests and/or patches against
 
['next' branch](https://gitorious.org/copyleft-org/tutorial/source/next:) are
 
['next' branch](https://k.copyleft.org/guide/changelog?branch=next) are
 
typically much preferred, and the workflow explanations below assume that.
 
However, merge requests and/or patches against
 
['master' branch](https://gitorious.org/copyleft-org/tutorial/source/master:)
 
['master' branch](https://k.copyleft.org/guide/changelog?branch=master)
 
are not necessarily rejected.  In fact, if your change is a fix for typo,
...
 
@@ -175,3 +176,3 @@ replace 'next' everywhere below with 'master'.
 

	
 
### Contributing via Gitorious
 
### Contributing via copyleft.org's Kallithea instance
 

	
...
 
@@ -179,9 +180,9 @@ First-time contributors may want to do the following four items first:
 

	
 
0. [Create an account on Gitorious](https://gitorious.org/users/new)
 
0. [Create an account on k.copyleft.org](https://k.copyleft.org/_admin/register)
 

	
 
1. [Visit gitorious.org/copyleft-org/tutorial](https://gitorious.org/copyleft-org/tutorial)
 
    and click "Clone".
 
1. [Visit k.copyleft.org/guide](https://k.copyleft.org/guide)
 
    and choose "Fork" from the "Options" menu.
 

	
 
    Instead of the default, you might call your clone
 
    "MYNAME-copyleft-tutorial-suggestions".
 
    "guide-USERNAME".
 

	
...
 
@@ -189,5 +190,5 @@ First-time contributors may want to do the following four items first:
 

	
 
        $ git clone git@gitorious.org:copyleft-org/MYNAME-copyleft-tutorial-suggestions.git copyleft-tutorial
 
        $ cd copyleft-tutorial
 
        $ git remote rename origin MYNAME-copyleft-tutorial-suggestions
 
        $ git clone https://USERNAME@k.copyleft.org/guide-USERNAME copyleft-guide
 
        $ cd copyleft-guide
 
        $ git remote rename origin guide-USERNAME
 

	
...
 
@@ -200,5 +201,5 @@ First-time contributors may want to do the following four items first:
 

	
 
        $ git remote add copyleft-tutorial-official git@gitorious.org:copyleft-org/tutorial.git
 
        $ git fetch copyleft-tutorial-official
 
        $ git branch --track official-next copyleft-tutorial-official/next
 
        $ git remote add guide-official https://bkuhn@k.copyleft.org/guide
 
        $ git fetch guide-official
 
        $ git branch --track official-next guide-official/next
 

	
...
 
@@ -224,4 +225,4 @@ request.
 
        $ git branch -D official-next
 
        $ git fetch copyleft-tutorial-official
 
        $ git branch --track official-next copyleft-tutorial-official/next
 
        $ git fetch guide-official
 
        $ git branch --track official-next gude-official/next
 
        $ git checkout official-next
...
 
@@ -260,3 +261,3 @@ request.
 

	
 
        $ git push MYNAME-copyleft-tutorial-suggestions my-new-idea-for-tutorial
 
        $ git push guide-USERNAME my-new-idea-for-tutorial
 

	
...
 
@@ -264,4 +265,4 @@ request.
 

	
 
5. Now, visit Gitorious' merge-request creation web interface at
 
   https://gitorious.org/copyleft-org/MYNAME-copyleft-tutorial-suggestions/merge_requests/new
 
5. Now, visit the Kallithea pull request merge-request creation web interface at
 
   https://k.copyleft.org/guide-USERNAME/pull-request
 

	
...
 
@@ -269,7 +270,6 @@ request.
 

	
 
        Summary:       Briefly describe your proposal
 
        Description:   More completely describe your proposal
 
        Target:        tutorial
 
        Target Branch: next
 
        Source Branch: my-new-idea-for-tutorial
 
        Title:                  Briefly describe your proposal
 
        Description:            More completely describe your proposal
 
        Original Repository:    guide-USERNAME : my-new-idea-for-tutorial
 
        Destination Repository: guide (parent) : next
 

	
README.md
Show inline comments
...
 
@@ -24,4 +24,4 @@ and [download a PDF of the Guide as well](http://copyleft.org/guide/comprehensiv
 
Note the
 
[canonical repository for this project is on gitorious](https://gitorious.org/copyleft-org/tutorial/source/master:).
 
Typically, copies of this repository on  sites other than gitorious are for informational and backup
 
[canonical repository for this project is on k.copyleft.org](https://k.copyleft.org/guide/files/tip/).
 
Typically, copies of this repository on  sites other than copyleft.org are for informational and backup
 
purposes only.
enforcement-case-studies.tex
Show inline comments
...
 
@@ -449,3 +449,3 @@ and waited approximately 40 minutes for the build to complete\footnote{Build
 
kept a
 
\href{https://gitorious.org/copyleft-org/tutorial/source/master:enforcement-case-studies_log-output/thinkpenguin_librecmc-complete.log}{full
 
\href{https://k.copyleft.org/guide/files/master/enforcement-case-studies_log-output/thinkpenguin_librecmc-complete.log}{full
 
  log of the build}, which is not included herein due its size (approximately
...
 
@@ -517,3 +517,3 @@ mips-librecmc-linux-uclibc-gcc.bin: /lib/libc.so.6:
 
   (The
 
\href{https://gitorious.org/copyleft-org/tutorial/source/master:enforcement-case-studies_log-output/thinkpenguin_u-boot-build_fail.log}{complete
 
\href{https://k.copyleft.org/guide/files/master/enforcement-case-studies_log-output/thinkpenguin_u-boot-build_fail.log}{complete
 
  log output from the failure} is too lengthy to include herein.)
...
 
@@ -538,3 +538,3 @@ $ ln -s \
 
The
 
\href{https://gitorious.org/copyleft-org/tutorial/source/master:enforcement-case-studies_log-output/thinkpenguin_u-boot-finish_build.log}{full
 
\href{https://k.copyleft.org/guide/files/master/enforcement-case-studies_log-output/thinkpenguin_u-boot-finish_build.log}{full
 
  log of the build} is not included herein due its size (approximately 3.8K
...
 
@@ -743,3 +743,3 @@ The comparison steps were as follows:
 
\item Extract the filesystem from the image we built by running
 
  \href{https://gitorious.org/copyleft-org/gpl-compliance-scripts/source/master:find-firmware.pl}{find-firmware.pl}
 
  \href{https://k.copyleft.org/gpl-compliance-scripts/files/master/find-firmware.pl}{find-firmware.pl}
 
  on ``bin/ar71xx/librecmc-ar71xx-generic-tl-wr841n-v8-squashfs-factory.bin''
third-party-citations.tex
Show inline comments
...
 
@@ -9,3 +9,3 @@ many contributions received via its
 
  contribution process}.  Please
 
\href{https://gitorious.org/copyleft-org/tutorial/history/master}{review its
 
\href{https://k.copyleft.org/guide/changelog}{review its
 
  Git logs} for full documentation of all contributions.
...
 
@@ -16,3 +16,3 @@ The specific methods and details of incorporation are fully
 
documented in the
 
\href{https://gitorious.org/copyleft-org/tutorial/history/master}{Git logs}
 
\href{https://k.copyleft.org/guide/changelog}{Git logs}
 
of the project.
...
 
@@ -49,3 +49,3 @@ herein included under their CC-By-SA licensing.  Thus, as the reader might
 
expect, the
 
\href{https://gitorious.org/copyleft-org/tutorial/history/master}{version
 
\href{https://k.copyleft.org/guide/changelog}{version
 
  control logs} contain the only true and accurate view available of who has
0 comments (0 inline, 0 general)