From: Milan Zamazal <pdm@zamazal.org>
To: Richard.Earnshaw@arm.com
Cc: gnats-devel@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: GNATS feature requests
Date: Mon, 09 Apr 2001 12:12:00 -0000 [thread overview]
Message-ID: <878zl99a9x.fsf@zamazal.org> (raw)
In-Reply-To: <200104090921.KAA08222@cam-mail2.cambridge.arm.com>
>>>>> "RE" == Richard Earnshaw <rearnsha@arm.com> writes:
RE> It would also be useful for the canonical PR to contain a
RE> reference to those PRs that are duplicates, just in case one of
RE> them happens to have additional pertinent information. A field
RE> such as "duplicates: <pr-list>" would do this.
Yes, there should be some way of linking of both the problems (kind of
virtual merge).
Milan Zamazal
--
Here is my advice, don't try to program the bleeding edge for the
general populace unless you really, really, really like migraines.
Neal H. Walfield
next prev parent reply other threads:[~2001-04-09 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 14:31 Bryce McKinlay
2001-04-08 11:28 ` Milan Zamazal
2001-04-09 2:22 ` Richard Earnshaw
2001-04-09 12:12 ` Milan Zamazal [this message]
2001-04-09 3:27 ` Bryce McKinlay
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=878zl99a9x.fsf@zamazal.org \
--to=pdm@zamazal.org \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=gnats-devel@sources.redhat.com \
/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.
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).