all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Debbugs handling of packages
Date: Sun, 12 Feb 2017 11:05:54 +0000	[thread overview]
Message-ID: <20170212110553.tby3igj4mud6hewo@wasp> (raw)
In-Reply-To: <20170208191546.GA1769@jurong>

On 17-02-08 20:15:46, Andreas Enge wrote:
> On Wed, Feb 08, 2017 at 03:29:31PM +0100, Ricardo Wurmus wrote:
> > Just a question: does this mean that patch *sets* should be flattened
> > before sending them so that they are part of the *same* debbugs issue
> > (instead of being scattered across as many issues as there are patches)?
> 
> This would be desirable, I think.
> 
> > E.g. for submitting the last 10 commits:
> >     git format-patch -10 --stdout > series.patch
> >     git send-email --to=guix-packages@gnu.org series.patch
> 
> Alternatively, one can send only the first patch. This will open a new issue,
> and the submitter obtains the bug number with the corresponding e-mail
> address in reply. Then one can send the remaining patches message by message
> to this address.
> 
> Andreas

Okay, the mailman list is now live, I assume the debbugs part is fixed
too reading in the child threads here. We now have to reflect the
suggested use as described in this email in the contributing guide and
inform the help and devel list about this change.

Thanks,
--
ng0 -- https://www.inventati.org/patternsinthechaos/

  reply	other threads:[~2017-02-12 11:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 19:09 Guix package incubator (later a channel) Pjotr Prins
2017-02-06 21:44 ` ng0
2017-02-07  5:42   ` Pjotr Prins
2017-02-07 18:59     ` Christopher Allan Webber
2017-02-07 20:37       ` ng0
2017-02-07 19:38 ` Ricardo Wurmus
2017-02-07 20:59   ` ng0
2017-02-08  6:58   ` Pjotr Prins
2017-02-08 13:46   ` Debbugs handling of packages Ludovic Courtès
2017-02-08 14:29     ` Ricardo Wurmus
2017-02-08 19:15       ` Andreas Enge
2017-02-12 11:05         ` ng0 [this message]
2017-02-09 23:12       ` Debbugs handling of Guix patches Ludovic Courtès
2017-02-10  0:40         ` Glenn Morris
2017-02-10 12:41           ` Ludovic Courtès
2017-02-10 17:41             ` Glenn Morris
2017-02-10 22:46               ` Ludovic Courtès
2017-02-11  1:43                 ` Christopher Allan Webber
2017-02-11 14:37                   ` New guix-patches mailing list not showing up on Mailman Ludovic Courtès
2017-02-11 22:11                     ` [Savannah-hackers-public] " Assaf Gordon
2017-02-11 22:51                     ` Karl Berry
2017-02-12 13:54                       ` Ludovic Courtès
2017-02-12  1:51                 ` Debbugs handling of Guix patches Glenn Morris
2017-02-12 14:01                   ` Ludovic Courtès
2017-02-26  8:42                     ` Pjotr Prins
2017-02-12 14:11           ` New guix-patches mailing list hooked to Debbugs! Ludovic Courtès

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=20170212110553.tby3igj4mud6hewo@wasp \
    --to=contact.ng0@cryptolab.net \
    --cc=andreas@enge.fr \
    --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.