all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>, guix-devel@gnu.org
Subject: Re: Emacs and URLs in Git commit messages
Date: Thu, 04 Feb 2021 14:16:57 +0100	[thread overview]
Message-ID: <864kisc6ra.fsf@gmail.com> (raw)
In-Reply-To: <87o8h0mdmt.fsf@gmail.com>

Hi Chris,

On Thu, 04 Feb 2021 at 00:38, Chris Marusich <cmmarusich@gmail.com> wrote:

>       Fixes <https://issues.guix.gnu.org/45314>.

[...]

> Regarding the URL, do people just type it all out, including the opening
> and closing brackets (<>)?  Or is there an Emacs command that does it
> for you?  I've briefly looked on the Internet, but this is the kind of
> thing that seems difficult to search for.

I am not representative since I commit few fixes.  Well, I have a tiny
helper that pushes to the kill ring:

<https://github.com/zimoun/my-conf/blob/master/.config/emacs/lisp/funs.el#L271>

Especially reading bug#45314 in Debbugs mode, I type “M-x
my/guix-issues” then the URL ’http://issues.guix.gnu.org/issue/45314’ is
stashed.  If not in debbugs mode, as here in message mode, the tiny
helper asks the bug number then pushes it to the kill ring.  This tiny
helper is far from perfect, any improvements is welcome. :-) Especially
if it is already provided by an Emacs command.

About the brackets, I type them.


Aside I thought the convention was <http://bugs.gnu.org/45314> tough for
bug fix commit.  Anyway.


Hope that helps,
simon


  parent reply	other threads:[~2021-02-04 13:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04  8:38 Emacs and URLs in Git commit messages Chris Marusich
2021-02-04  9:15 ` Maxime Devos
2021-02-06  5:00   ` Chris Marusich
2021-02-04 13:16 ` zimoun [this message]
2021-02-04 19:12 ` Bengt Richter
2021-02-05 10:40 ` Ludovic Courtès
2021-04-21  3:09   ` Maxim Cournoyer
2021-05-07  9:20     ` Alexey Abramov

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=864kisc6ra.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@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 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.