From: reader@newsguy.com
Subject: Re: Piping a patch to patchee
Date: Thu, 22 Jun 2006 21:50:35 -0500 [thread overview]
Message-ID: <87u06clh50.fsf@newsguy.com> (raw)
In-Reply-To: <microsoft-free.87ejxgpz1w.fsf@youngs.au.com>
Steve Youngs <steve@sxemacs.org> writes:
> * reader <reader@newsguy.com> writes:
>
> > I think I remember sending patches from a artile buffer to the
> > directory and target of the patch from gnus somehow.
>
> I just use `M-x ediff-patch-file' from the summary buffer. It
> defaults to asking if the patch is in the article buffer (well it does
> for me).
Yup, thats the one I was remembering... thanks.
prev parent reply other threads:[~2006-06-23 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 17:30 reader
2006-06-22 21:15 ` Reiner Steib
2006-06-23 2:46 ` reader
2006-06-22 23:10 ` Steve Youngs
2006-06-23 2:50 ` reader [this message]
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=87u06clh50.fsf@newsguy.com \
--to=reader@newsguy.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.
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 NNTP newsgroup(s).