From: Junio C Hamano <junkio@cox.net>
To: Carl Worth <cworth@cworth.org>
Cc: Jari Aalto <jari.aalto@cante.net>, git@vger.kernel.org
Subject: Re: FEATURE REQUEST: git-format-path: Add option to encode patch content
Date: Fri, 27 Apr 2007 14:28:50 -0700 [thread overview]
Message-ID: <7vk5vxmrql.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <87y7kdo6pn.wl%cworth@cworth.org> (Carl Worth's message of "Fri, 27 Apr 2007 14:20:04 -0700")
Carl Worth <cworth@cworth.org> writes:
> My MUA doesn't have support (that I know of) for piping a sequence of
> messages to a command. Do your MUAs? If not, how do people generally
> handle long sequences of [n/N] patch emails?
Are you asking _me_ specifically? Assuming so,
Yes, my MUA does allow "next N messages" or "selected messages"
to be given to an external program.
But I typically save them in a separate mailbox for reviewing
and in-editor fixups before applying, so "next N messages" are
useful to me for saving but not applying.
next prev parent reply other threads:[~2007-04-27 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 11:31 FEATURE REQUEST: git-format-path: Add option to encode patch content Jari Aalto
2007-04-27 13:43 ` Johannes Schindelin
2007-04-27 17:33 ` Jari Aalto
2007-04-27 19:29 ` Alex Riesen
2007-04-28 2:53 ` Johannes Schindelin
2007-04-27 19:49 ` Junio C Hamano
2007-04-27 20:35 ` Robin H. Johnson
2007-04-27 21:20 ` Carl Worth
2007-04-27 21:28 ` Junio C Hamano [this message]
2007-04-27 21:40 ` Linus Torvalds
2007-04-27 22:55 ` Carl Worth
2007-04-27 23:41 ` Linus Torvalds
2007-04-27 23:47 ` Linus Torvalds
2007-04-27 23:58 ` Carl Worth
2007-04-28 0:20 ` Linus Torvalds
2007-04-28 0:53 ` Junio C Hamano
2007-04-30 22:01 ` Carl Worth
2007-04-28 0:56 ` Junio C Hamano
2007-04-30 22:00 ` Carl Worth
2007-04-30 22:18 ` Junio C Hamano
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=7vk5vxmrql.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
/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.
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.