--- Begin Message ---
|
Subject: |
[PATCH] HACKING: Describe address@hidden as the list for patches. |
|
Date: |
Tue, 28 Feb 2017 11:51:20 +0000 |
From: ng0 <address@hidden>
---
HACKING | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/HACKING b/HACKING
index 1e0bddfaf..76568cfcb 100644
--- a/HACKING
+++ b/HACKING
@@ -5,6 +5,7 @@
Copyright © 2012, 2013, 2014, 2016 Ludovic Courtès <address@hidden>
Copyright © 2015, 2017 Mathieu Lirzin <address@hidden>
Copyright © 2017 Leo Famulari <address@hidden>
+Copyright © 2017 ng0 <address@hidden>
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
@@ -25,8 +26,9 @@ convenient. When you deem it necessary, feel free to ask for
it on the
mailing list. When you get commit access, please make sure to follow the
policy below (discussions of the policy can take place on address@hidden)
-Non-trivial patches should always be posted to address@hidden (trivial
-patches include fixing typos, etc.)
+Non-trivial patches should always be posted to address@hidden (trivial
+patches include fixing typos, etc.). The patches sent to this list can be
+tracked in its
[[https://debbugs.gnu.org/cgi/pkgreport.cgi?pkg=guix-patches][debbugs
webinterface]].
For patches that just add a new package, and a simple one, it’s OK to commit,
if you’re confident (which means you successfully built it in a chroot setup,
--
2.12.0
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#25899: [PATCH] HACKING: Describe address@hidden as the list for patches. |
|
Date: |
Wed, 15 Mar 2017 17:01:39 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Ricardo Wurmus <address@hidden> skribis:
> ng0 <address@hidden> writes:
>
>>> Commit 230efa876fea3b38f78502bd759b2943651929de updated the manual to
>>> mention guix-patches. Do we need anything more?
>>
>> Apparently yes, as people still send patches to guix-devel and at the
>> time when I wrote this patch were not aware of guix-patches.
>
> I agree. It would be good to mention “guix-patches” in HACKING. To me,
> patches that are in “guix-patches” have a much lower risk to be drowned
> out by other discussions.
Done in bc551cf32b6ccb3f8dd60b1d0d4e3c3e88cb1f8d!
Ludo'.
--- End Message ---