unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Try using block/unblock for bugs relevant to releases
Date: Wed, 04 Feb 2015 13:58:57 -0500	[thread overview]
Message-ID: <81twz18pvy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvlhkdafwm.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 04 Feb 2015 09:51:58 -0500")

Stefan Monnier wrote:

>> So I suggest trying instead the "block/unblock" feature, and to that end
>> created bug#19758 and 19759 for tracking bugs relevant to 24.5 and 25.1,
>> respectively. I added a small number of items to get started;
>> feel free to add your own.
>
> Can you give a little primer for how to use those?

Say bug 123 is one that needs to be fixed for Emacs 24.5.
Send a message to control that says:

block 19758 by 123

That's basically it. Closing 123 when it is fixed is still the right thing.
If you made a mistake, s/block/unblock to undo it.

You can see the blocking bugs at http://debbugs.gnu.org/19758 .



  reply	other threads:[~2015-02-04 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04  1:25 Try using block/unblock for bugs relevant to releases Glenn Morris
2015-02-04 14:51 ` Stefan Monnier
2015-02-04 18:58   ` Glenn Morris [this message]
2015-02-04 21:49     ` Stefan Monnier
2015-02-04 23:32       ` Glenn Morris
2015-02-05  8:53         ` Michael Albinus
2015-02-05  8:44     ` Michael Albinus
2015-02-17 23:24       ` Dmitry Gutov
2015-02-18  8:35         ` Michael Albinus

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81twz18pvy.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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/emacs.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).