From: Leo Famulari <leo@famulari.name>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 28141@debbugs.gnu.org
Subject: [bug#28141] [PATCH] doc: Mention how to use emacs-debbugs.
Date: Fri, 18 Aug 2017 16:09:57 -0400 [thread overview]
Message-ID: <20170818200957.GA1244@jasmine.lan> (raw)
In-Reply-To: <50d34d92.AEAAOkOFBSMAAAAAAAAAAAOtUOAAAAACwQwAAAAAAAW9WABZl0Ov@mailjet.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Sat, Aug 19, 2017 at 01:11:16AM +0530, Arun Isaac wrote:
> * HACKING (Using emacs-debbugs): Add section on using emacs-debbugs.
> ---
> HACKING | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/HACKING b/HACKING
> index 20cc9ea6e..e674f4428 100644
> --- a/HACKING
> +++ b/HACKING
> @@ -61,3 +61,12 @@ after two weeks, and if you’re confident, it’s OK to commit.
>
> That last part is subject to being adjusted, allowing individuals to commit
> directly on non-controversial changes on parts they’re familiar with.
> +
> +* Using emacs-debbugs
> +
> +Bug reports and patches are tracked using debbugs. If you are on emacs, you
> +can use emacs-debbugs.
> +
> +List all open bug reports on guix-patches with
> +
> +C-u M-x debbugs-gnu <RET> <RET> guix-patches <RET> n y
LGTM
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-18 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 19:41 [bug#28141] [PATCH] doc: Mention how to use emacs-debbugs Arun Isaac
2017-08-18 20:09 ` Leo Famulari [this message]
2017-08-18 20:22 ` Marius Bakke
2017-08-19 8:14 ` bug#28141: " Arun Isaac
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170818200957.GA1244@jasmine.lan \
--to=leo@famulari.name \
--cc=28141@debbugs.gnu.org \
--cc=arunisaac@systemreboot.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/guix.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).