From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: ahyatt@gmail.com, emacs-devel@gnu.org
Subject: Re: Basic questions about the triage process
Date: Thu, 31 Dec 2015 05:38:18 +0200 [thread overview]
Message-ID: <83oad7b845.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-8czb+xe2ykLNZ-8jJJETaLRbMqAHJ+8+vzHf9UQC6OgQ@mail.gmail.com> (message from Noam Postavsky on Wed, 30 Dec 2015 20:19:27 -0500)
> Date: Wed, 30 Dec 2015 20:19:27 -0500
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Cc: Andrew Hyatt <ahyatt@gmail.com>, emacs-devel@gnu.org
>
> On Wed, Dec 30, 2015 at 12:21 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > One needs to read the error message and resubmit the control message
> > modified as appropriate. E.g., one example I tend to bump into is
> > when I merge a bug with another one, and debbugs refuses because their
> > state is different -- in that case one needs to change the state of
> > one of the two bugs and then resubmit the merge directive.
>
> Is there some reason not to use forcemerge?
It still requires a new control message, so what I said is still
valid. And as long as you do have to send a new control message, why
not do it right?
Also, note this caveat:
> Note: you cannot merge with an archived bug - you must unarchive it first.
IOW, even forcemerge won't always work.
next prev parent reply other threads:[~2015-12-31 3:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 5:39 Basic questions about the triage process Andrew Hyatt
2015-12-28 8:58 ` Michael Albinus
2015-12-28 16:25 ` Andrew Hyatt
2015-12-28 17:35 ` Michael Albinus
2015-12-28 20:24 ` John Wiegley
2015-12-29 5:40 ` Andrew Hyatt
2015-12-29 17:12 ` Eli Zaretskii
2015-12-30 0:22 ` Andrew Hyatt
2015-12-30 17:21 ` Eli Zaretskii
2015-12-31 1:19 ` Noam Postavsky
2015-12-31 3:38 ` Eli Zaretskii [this message]
2015-12-31 9:06 ` Michael Albinus
2015-12-31 13:49 ` Eli Zaretskii
2015-12-31 13:57 ` Michael Albinus
2016-01-07 21:04 ` Phillip Lord
2016-01-07 22:05 ` Andy Moreton
2016-01-07 22:40 ` Phillip Lord
2016-01-09 3:46 ` Andrew Hyatt
2015-12-28 23:55 ` Xue Fuqiao
2015-12-29 0:38 ` Andrew Hyatt
2015-12-29 0:50 ` Lars Ingebrigtsen
2015-12-29 0:59 ` Andrew Hyatt
2015-12-29 1:07 ` Lars Ingebrigtsen
2015-12-29 1:21 ` John Wiegley
2015-12-29 1:50 ` Drew Adams
2016-01-02 21:37 ` Marcin Borkowski
2016-02-15 20:04 ` Marcin Borkowski
2015-12-29 6:46 ` CHENG Gao
2015-12-29 15:50 ` Eli Zaretskii
2015-12-29 17:03 ` Nikolaus Rath
2015-12-29 17:16 ` John Wiegley
2015-12-29 17:50 ` Drew Adams
2015-12-29 23:36 ` Andrew Hyatt
2016-01-07 21:09 ` Phillip Lord
2016-01-07 21:28 ` Lars Magne Ingebrigtsen
2016-01-09 3:47 ` Andrew Hyatt
2016-01-09 20:56 ` John Wiegley
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=83oad7b845.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ahyatt@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).