From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Proposal to use usertags rather than packages on debbugs.gnu.org
Date: Sat, 05 Dec 2009 16:36:00 -0500 [thread overview]
Message-ID: <gtskbpw1bz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <7dhbs5ce1p.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 05 Dec 2009 16:21:38 -0500")
BTW, anyone should feel free to play around with tagging, closing,
reassigning, submitting etc on debbugs.gnu.org. The data will all get
blown away when a final rsync from the older server is done.
next prev parent reply other threads:[~2009-12-05 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 20:06 Proposal to use usertags rather than packages on debbugs.gnu.org Glenn Morris
2009-12-05 21:01 ` Stefan Monnier
2009-12-05 21:21 ` Glenn Morris
2009-12-05 21:31 ` Glenn Morris
2009-12-05 21:36 ` Glenn Morris [this message]
2009-12-05 21:39 ` Glenn Morris
2009-12-13 23:59 ` Glenn Morris
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=gtskbpw1bz.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).