all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>,
	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 22:22:58 +0200	[thread overview]
Message-ID: <87r2w8y6al.fsf@fastmail.com> (raw)
In-Reply-To: <20170818200957.GA1244@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

Leo Famulari <leo@famulari.name> writes:

> 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

Yes, good idea :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-08-18 20:24 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
2017-08-18 20:22   ` Marius Bakke [this message]
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

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

  git send-email \
    --in-reply-to=87r2w8y6al.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=28141@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.