From: Petter <petter@mykolab.ch>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Doc: reference to guix-devel for submitting patches
Date: Sun, 30 Apr 2017 18:21:17 +0200 [thread overview]
Message-ID: <20170430182117.5c235a3d@mykolab.ch> (raw)
In-Reply-To: <87inlmhaq8.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Hi Chris,
On Sat, 29 Apr 2017 19:48:15 -0700
Chris Marusich <cmmarusich@gmail.com> wrote:
>
> Yes, this wording is unclear. It could be interpreted as an invitation
> to send bug reports and patches to guix-devel@, which is not quite
> right.
>
> On related note, I see there is a section on submitting patches ((guix)
> Submitting Patches), but there is no similar, dedicated, section on
> submitting bugs (i.e., to bug-guix).
>
> >
> > 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?
> >
>
> Seems to me like we should clarify the wording in the "Contributing"
> section. And maybe we should add a "Submitting Bug Reports"
> sub-section, similar to the "Submitting Patches" one.
>
> Do you think you could try your hand at writing this?
>
Alright, I'll give it a go. Will post to guix-patches then.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-30 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 16:02 Doc: reference to guix-devel for submitting patches Petter
2017-04-26 19:45 ` Maxim Cournoyer
2017-04-30 2:48 ` Chris Marusich
2017-04-30 16:21 ` Petter [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170430182117.5c235a3d@mykolab.ch \
--to=petter@mykolab.ch \
--cc=cmmarusich@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.