From: "Rafael Laboissière" <rafael@laboissiere.net>
To: emacs-orgmode@gnu.org
Subject: Pushing commits to the Work Git repository
Date: Wed, 6 Feb 2019 16:42:21 +0100 [thread overview]
Message-ID: <20190206154221.GV22582@laboissiere.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 220 bytes --]
Hi,
Is there any policy for pushing commits to the Worg Git repository? I
fixed the GitHub paths in file org-outside-org.org, as per the patch
attached to this message and would like to contribute it.
Best,
Rafael
[-- Attachment #2: 0001-Transfer-maintainership-of-outshine-outorg-and-navi-.patch --]
[-- Type: text/x-diff, Size: 2153 bytes --]
From 1458b431c347fdf53ce84eecc2e2503385e93984 Mon Sep 17 00:00:00 2001
From: Rafael Laboissiere <rafael@laboissiere.net>
Date: Wed, 6 Feb 2019 16:33:36 +0100
Subject: [PATCH] Transfer maintainership of outshine, outorg, and navi-mode
---
org-tutorials/org-outside-org.org | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/org-tutorials/org-outside-org.org b/org-tutorials/org-outside-org.org
index 8fe2ae92..b8bc5606 100644
--- a/org-tutorials/org-outside-org.org
+++ b/org-tutorials/org-outside-org.org
@@ -134,8 +134,8 @@ To sum it up in one sentence:
Download =outshine.el= (or clone the github-repo) and copy it to a location
where Emacs can find it:
-| https://github.com/tj64/outshine |
-| git clone git@github.com:tj64/outshine.git |
+| https://github.com/alphapapa/outshine |
+| git clone git@github.com:alphapapa/outshine.git |
Use this in your '.emacs' to get started:
@@ -323,8 +323,8 @@ works too).
You can download the file (or clone the github-repo) here:
-| https://github.com/tj64/outorg |
-| git clone git@github.com:tj64/outorg.git |
+| https://github.com/alphapapa/outorg |
+| git clone git@github.com:alphapapa/outorg.git |
/outorg/ requires Org-mode too, thus should be loaded after Org-mode. Insert
@@ -597,10 +597,10 @@ offering a vast amount of possible 'views' at the original-buffer.
Download (or clone the github-repos of) the three required libraries
-| `navi-mode.el' | https://github.com/tj64/navi |
-| | git clone git@github.com:tj64/navi.git |
-| `outshine.el' | https://github.com/tj64/outshine |
-| `outorg.el' | https://github.com/tj64/outorg |
+| `navi-mode.el' | https://github.com/alphapapa/navi |
+| | git clone git@github.com:alphapapa/navi.git |
+| `outshine.el' | https://github.com/alphapapa/outshine |
+| `outorg.el' | https://github.com/alphapapa/outorg |
and put them in a place where Emacs can find them (on the Emacs 'load-path').
Follow the installation instructions in =outshine.el= and =outorg.el=.
--
2.19.2
reply other threads:[~2019-02-06 16:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190206154221.GV22582@laboissiere.net \
--to=rafael@laboissiere.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).