From: Bart Trojanowski <bart@jukie.net>
To: Carl Worth <cworth@cworth.org>,
Tassilo Horn <tassilo@member.fsf.org>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] Return unpropertized strings for filename and message-id
Date: Fri, 27 Nov 2009 18:31:23 -0500 (EST) [thread overview]
Message-ID: <20091127233123.3A4FE205E5065@oxygen.jukie.net> (raw)
In-Reply-To: <87k4xdq7ys.fsf@yoom.home.cworth.org>
[[ First of all I am jazzed because this is the first email I am sending to
anyone other than myself from the vim interface to notmuch ]]
Getting on wit the show...
> So to satisfy "git am", introductory and explanatory portions of
> the email, ("Hi!" and "Here's my first patch"), have to be
> relegated to past the "---" divider).
>
> I actually don't love this about "git am", since I think those
> introductory parts are essential to having cordial and friendly
> exchanges on the mailing list, (rather than just dryly shooting
> code back and forth). And it feels natural to have them first. One
> thing that might be interesting is to teach "git am" about an
> additional divider so that other text can came *before* the commit
> message.
>
> Alternately, one can put introductory text in one message, and the
> dry commit-only stuff as a reply.
You can actually put arbitrary text between the diffstat output and the first
diff --git line. For example:
--- 8< ---
From e6628e78d9ce3f9383a4699df9063a648617b428 Mon Sep 17 00:00:00 2001
From: Bart Trojanowski <bart@jukie.net>
Date: Fri, 27 Nov 2009 18:02:05 -0500
Subject: [PATCH] this is the patch description
Text that goes here will end up in the git commit.
---
vim/README | 3 ++-
1 files changed, 11 insertions(+), 12 deletions(-)
Anything that goes here will be ignored, so you can typ
diff --git a/vim/README b/vim/README
index 299c7f8..8cd3b1a 100644
--- a/vim/README
+++ b/vim/README
@@ -42,7 +42,8 @@ Buffer types:
You are presented with the search results when you run :NotMuch.
Keybindings:
- <Enter> - show the selected message
+ <Space> - show the selected thread colapsing unmatched items
+ <Enter> - show the entire selected thread
a - archive message (remove inbox tag)
f - filter the current search terms
o - toggle search screen order
--
1.6.4.4.2.gc2f148
--- 8< ---
--
email sent from notmuch.vim plugin
next prev parent reply other threads:[~2009-11-27 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 16:57 [PATCH] Return unpropertized strings for filename and message-id Tassilo Horn
2009-11-26 21:42 ` Carl Worth
2009-11-27 8:13 ` Tassilo Horn
2009-11-28 4:03 ` Carl Worth
2009-11-27 23:31 ` Bart Trojanowski [this message]
2009-11-27 23:41 ` Bart Trojanowski
2009-11-28 5:56 ` Carl Worth
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091127233123.3A4FE205E5065@oxygen.jukie.net \
--to=bart@jukie.net \
--cc=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
--cc=tassilo@member.fsf.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://yhetil.org/notmuch.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).