From: Arun Isaac <arunisaac@systemreboot.net>
To: 71481@debbugs.gnu.org
Cc: "Arun Isaac" <arunisaac@systemreboot.net>,
"Florian Pelz" <pelzflorian@pelzflorian.de>,
"Ludovic Courtès" <ludo@gnu.org>,
"Matthew Trzcinski" <matt@excalamus.com>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#71481] [PATCH 1/3] doc: Document mumi am, compose and www subcommands.
Date: Mon, 10 Jun 2024 14:19:47 +0100 [thread overview]
Message-ID: <64b211c1bcab088e6502df4c824f91a28a6aa9e5.1718025563.git.arunisaac@systemreboot.net> (raw)
* doc/contributing.texi (Debbugs User Interfaces)[Command-line interface]:
Document mumi am, compose and www subcommands.
* doc/guix.texi: Bump copyright year.
Change-Id: I28bde9454ad35115ed60fe4d6ffa35fad599b2d1
---
doc/contributing.texi | 70 ++++++++++++++++++++++++++++++++++++-------
doc/guix.texi | 2 +-
2 files changed, 61 insertions(+), 11 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index b8adc169d8..1fdf9b4db5 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -2395,9 +2395,9 @@ Debbugs User Interfaces
@subsubsection Command-line interface
Mumi also comes with a command-line interface that can be used to search
-existing issues, open new issues and send patches. You do not need to
-use Emacs to use the mumi command-line client. You interact with it
-only on the command-line.
+existing issues, open new issues, compose replies, apply and send
+patches. You do not need to use Emacs to use the mumi command-line
+client. You interact with it only on the command-line.
To use the mumi command-line interface, navigate to a local clone of the
Guix git repository, and drop into a shell with mumi, git and
@@ -2434,8 +2434,61 @@ Debbugs User Interfaces
opened on 24 Jan 09:42 Z by Efraim Flashner
@end example
-Once an issue is the current issue, you can easily create and send
-patches to it using
+Once an issue is the current issue, you can open the issue in a web
+browser, compose replies, apply patches, send patches, etc. with short
+succinct commands.
+
+Open the issue in your web browser using
+
+@example
+~/guix [env]$ mumi www
+@end example
+
+Compose a reply using
+
+@example
+~/guix [env]$ mumi compose
+@end example
+
+Compose a reply and close the issue using
+
+@example
+~/guix [env]$ mumi compose --close
+@end example
+
+@command{mumi compose} opens your mail client by passing @samp{mailto:}
+URIs to @command{xdg-open}. So, you need to have @command{xdg-open} set
+up to open your mail client correctly.
+
+Apply the latest patchset from the issue using
+
+@example
+~/guix [env]$ mumi am
+@end example
+
+You may also apply a patchset of a specific version (say, v3) using
+
+@example
+~/guix [env]$ mumi am v3
+@end example
+
+Or, you may apply a patch from a specific e-mail message. For example,
+to apply the patch from the 4th message (message index starts from 0),
+run
+
+@example
+~/guix [env]$ mumi am @@4
+@end example
+
+@command{mumi am} is a wrapper around @command{git am}. You can pass
+@command{git am} arguments to it after a @samp{--}. For example, to add
+a Signed-off-by trailer, run
+
+@example
+~/guix [env]$ mumi am -- -s
+@end example
+
+Create and send patches to the issue using
@example
~/guix [env]$ git format-patch origin/master
@@ -2452,11 +2505,8 @@ Debbugs User Interfaces
~/guix [env]$ mumi new
@end example
-and send patches
-
-@example
-~/guix [env]$ mumi send-email foo.patch bar.patch
-@end example
+and send an email (using @command{mumi compose}) or patches (using
+@command{mumi send-email}).
@command{mumi send-email} is really a wrapper around @command{git
send-email} that automates away all the nitty-gritty of sending patches.
diff --git a/doc/guix.texi b/doc/guix.texi
index 769ca1399f..e1d1d4696c 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -53,7 +53,7 @@
Copyright @copyright{} 2017–2022 Tobias Geerinckx-Rice@*
Copyright @copyright{} 2017 George Clemmer@*
Copyright @copyright{} 2017 Andy Wingo@*
-Copyright @copyright{} 2017, 2018, 2019, 2020, 2023 Arun Isaac@*
+Copyright @copyright{} 2017, 2018, 2019, 2020, 2023, 2024 Arun Isaac@*
Copyright @copyright{} 2017 nee@*
Copyright @copyright{} 2018 Rutger Helling@*
Copyright @copyright{} 2018, 2021, 2023 Oleg Pykhalov@*
base-commit: df5648daa1a5d097a430131bbff353b865b476b6
--
2.45.1
next reply other threads:[~2024-06-10 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 13:19 Arun Isaac [this message]
2024-06-10 17:41 ` [bug#71481] [PATCH 2/3] doc: Add mumi CLI concept index entries Arun Isaac
2024-06-12 14:50 ` Maxim Cournoyer
2024-06-10 17:41 ` [bug#71481] [PATCH 3/3] doc: Refer to mumi send-email in Submitting Patches Arun Isaac
2024-06-12 14:53 ` Maxim Cournoyer
2024-06-12 14:52 ` [bug#71481] [PATCH 1/3] doc: Document mumi am, compose and www subcommands Maxim Cournoyer
2024-06-12 21:17 ` bug#71481: " 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=64b211c1bcab088e6502df4c824f91a28a6aa9e5.1718025563.git.arunisaac@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=71481@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=matt@excalamus.com \
--cc=maxim.cournoyer@gmail.com \
--cc=pelzflorian@pelzflorian.de \
/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).