From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22587@debbugs.gnu.org
Subject: bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change
Date: Thu, 21 Apr 2016 13:40:03 +0300 [thread overview]
Message-ID: <87eg9z9rek.fsf@gmail.com> (raw)
In-Reply-To: <87shygthz8.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 20 Apr 2016 17:31:07 +0200")
Ludovic Courtès (2016-04-20 18:31 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> Ludovic Courtès (2016-04-19 13:50 +0300) wrote:
>>
>>> Yes, using the ‘retitle’ command, described somewhere at
>>> <http://debbugs.gnu.org/Developer.html>.
>>
>> Sorry, I don't see any mention of 'retitle' there, also I don't find
>> retitle control message while using emacs-debbugs package.
>
> Sorry, it’s at <http://debbugs.gnu.org/server-control.html>.
Thanks! And sorry for bothering, I should have found it myself. I
didn't realize that debbugs is such a featureful bug-tracker.
>>> However, I think (1) the title should describe the bug, not the
>>> solution, and (2) ‘guix edit’ does what it says IMO, even if it can
>>> occasionally stumble upon read-only files.
>>
>> OK, well I don't know what to do with it then. What about the following
>> title: «"guix edit" name may be confusing»?
>
> Perfect! :-)
Done.
--
Alex
next prev parent reply other threads:[~2016-04-21 10:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 18:04 bug#22587: ‘guix edit’ & ‘M-x guix-edit' typo, rename, & mode change myglc2
2016-02-07 18:58 ` Andreas Enge
2016-02-07 19:22 ` myglc2
2016-02-07 19:34 ` Andreas Enge
2016-02-07 20:26 ` myglc2
2016-02-08 8:34 ` Alex Kost
2016-02-08 15:30 ` Ludovic Courtès
2016-02-08 18:29 ` myglc2
2016-04-18 8:37 ` Alex Kost
2016-04-18 17:41 ` Ludovic Courtès
2016-04-19 8:18 ` Alex Kost
2016-04-19 10:50 ` Ludovic Courtès
2016-04-20 7:20 ` Alex Kost
2016-04-20 15:31 ` Ludovic Courtès
2016-04-21 10:40 ` Alex Kost [this message]
2016-06-02 19:40 ` Ludovic Courtès
2016-06-03 19:04 ` Alex Kost
2016-06-04 11:21 ` Ludovic Courtès
2016-04-18 21:10 ` myglc2
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=87eg9z9rek.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=22587@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).