all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Bengt Richter <bokr@bokr.com>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Assisting reviewing & committing with tags?
Date: Tue, 15 Feb 2022 17:23:23 +0100	[thread overview]
Message-ID: <375878a046ddd194cad9e9ec8813b2241e7d1cb7.camel@telenet.be> (raw)
In-Reply-To: <20220215122313.GA12713@LionPure>

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

Bengt Richter schreef op di 15-02-2022 om 13:23 [+0100]:
> Hi guix,
> 
> It sounds like a good idea, but ISTM we don't need yet another markup syntax
> if emacs org mode already defines a useful standard that can be adopted.
> 
> The advantage to org mode style [0] -- in commit commentary as well as tags
> would be its scrapability -- i.e., ease of writing an extractor/formatter
> for handy report snippets/pages and web stuff etc., whether implemented
> using foreign shell or within guix.

FYI, I think you responded to the wrong thread.  This thread was about
additional usertags in debbugs for reviewing in Guix, not about markup
languages or org mode.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-02-15 16:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 10:54 Assisting reviewing & committing with tags? Maxime Devos
2022-01-11 19:10 ` Leo Famulari
2022-02-02 13:58   ` Maxim Cournoyer
2022-02-15 12:23     ` Bengt Richter
2022-02-15 16:23       ` Maxime Devos [this message]
2022-03-21  8:47         ` Bengt Richter
2022-05-03 11:03   ` Debbugs usertags with Mumi or Emacs (was: Assisting reviewing & committing with tags?) zimoun
2022-05-03 16:10     ` Maxime Devos
2022-05-03 17:39     ` 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=375878a046ddd194cad9e9ec8813b2241e7d1cb7.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.