From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: guile-devel@gnu.org
Subject: [PATCH] add instructions for sending patches to Guile
Date: Sat, 20 Jul 2024 15:16:07 +0200 [thread overview]
Message-ID: <87le1wkxuw.fsf@web.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 221 bytes --]
Hi,
on the website, contribution section
( <https://www.gnu.org/software/guile/contribute/> )
we say how to report bugs, but we do not say how to contribute
improvements.
The attached patch adds the such instructions.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-Add-instructions-for-sending-patches.patch --]
[-- Type: text/x-patch, Size: 1705 bytes --]
From 64d69ecd3367768ca0a082c765a2f2b5ff811f2d Mon Sep 17 00:00:00 2001
From: Arne Babenhauserheide <arne_bab@web.de>
Date: Sat, 11 Dec 2021 16:12:17 +0100
Subject: [PATCH] Add instructions for sending patches
---
website/apps/base/contribute-page.scm | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/website/apps/base/contribute-page.scm b/website/apps/base/contribute-page.scm
index 630f05c..78441bf 100644
--- a/website/apps/base/contribute-page.scm
+++ b/website/apps/base/contribute-page.scm
@@ -60,6 +60,22 @@
"are available in "
(a (@ (href "https://savannah.gnu.org/git/?group=guile"))
"Git repositories") " at Savannah.")
+ (h2 (@ (id "patches")) "Sending patches")
+ (p "To contribute small improvements, please send patches to "
+ (a (@ (href "mailto:guile-devel@gnu.org")) "guile-devel@gnu.org")
+ ".")
+ (ul
+ (li "Please send a patch and commit log as produced by "
+ (code "git format-patch") ".")
+ (li "Please include a "
+ (a (@ (href "http://www.gnu.org/prep/standards/standards.html#Change-Logs")) "ChangeLog-style commit log")
+ " with your patch.")
+ (li "If the patch changes more than about ten lines of code, we "
+ "may ask you to assign your copyright to the FSF before it can "
+ "be applied."))
+ (p "For larger changes, please discuss them first in the "
+ (a (@ (href "https://mail.gnu.org/mailman/listinfo/guile-devel/")) "development mailing list")
+ ".")
(h2 (@ (id "bugs")) "Reporting bugs")
(p "You do us a much-appreciated service when you report the bugs "
"you find in Guile. Please don't assume we already know about "
--
2.45.1
[-- Attachment #1.3: Type: text/plain, Size: 216 bytes --]
Is this OK? Is there something I should change?
Do we want patches sent to bug-guile instead of guile-devel?
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
reply other threads:[~2024-07-20 13:16 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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87le1wkxuw.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-devel@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.
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).