From: Petter <petter@mykolab.ch>
To: guix-devel@gnu.org
Subject: Doc: reference to guix-devel for submitting patches
Date: Wed, 26 Apr 2017 18:02:09 +0200 [thread overview]
Message-ID: <20170426180210.1efae0c4@mykolab.ch> (raw)
Hi Guix,
I quite recently realized I sent a couple of patches to guix-devel, whereas
they should now go to guix-patches. I use the online manual and the current
state is that there's a couple of references to guix-devel for submitting
patches.
https://www.gnu.org/software/guix/manual/html_node/Submitting-Patches.html#Submitting-Patches
>We welcome contributions in the form of patches as produced by git format-patch
> sent to the mailing list
Where "mailing list" is mailto:guix-devel@gnu.org. This is updated in the
repository however, so I assume the online manual will reflect this shortly.
But here,
https://www.gnu.org/software/guix/manual/html_node/Contributing.html#Contributing
it says
> Please get in touch with us on guix-devel@gnu.org and #guix on the Freenode
> IRC network. We welcome ideas, bug reports, patches, and anything that may be
> helpful to the project.
And here,
https://www.gnu.org/software/guix/manual/html_node/Packaging-Guidelines.html#Packaging-Guidelines
the user is referred to the Contributing node.
> Once your package builds correctly, please send us a patch (see Contributing).
I think at least one of the latter two nodes could use an update to better
inform the soon-to-be-contributor that patches should go to guix-patches. Not
sure what the better fix is though.
What do you think?
Best,
Petter
next reply other threads:[~2017-04-26 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 16:02 Petter [this message]
2017-04-26 19:45 ` Doc: reference to guix-devel for submitting patches Maxim Cournoyer
2017-04-30 2:48 ` Chris Marusich
2017-04-30 16:21 ` Petter
2017-04-30 19:35 ` Leo Famulari
2017-04-30 20:03 ` Chris Marusich
2017-05-01 16:45 ` myglc2
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170426180210.1efae0c4@mykolab.ch \
--to=petter@mykolab.ch \
--cc=guix-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).