public inbox for
help / color / mirror / Atom feed
Subject: gnats/413: should support tracking PRs against many releases of code.
Date: Thu, 05 Sep 2002 15:13:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         413
>Category:       gnats
>Synopsis:       should support tracking PRs against many releases of code.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 05 18:12:26 -0400 2002
>Originator:     David Maxwell


Since each gnats PR can only have one software version coded against it,
it is difficult to track bugs which are resolved on the
HEAD, but not on older release branches, etc.
Maintain multiple branches of code. File a PR. Does it apply
to more than one branch? What about if it should be 'closed'
on one branch, but only 'analyzed' on another...


Gnats-prs mailing list

                 reply	other threads:[~2002-09-05 22:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

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

  git send-email \ \ \ \ \ \

* 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).