From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Piping a patch to patchee
Date: Thu, 22 Jun 2006 23:15:07 +0200 [thread overview]
Message-ID: <v91wtgzyck.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <877j39qes3.fsf@newsguy.com>
On Thu, Jun 22 2006, reader@newsguy.com wrote:
> I think I remember sending patches from a artile buffer to the
> directory and target of the patch from gnus somehow.
>
> Full searches in gnus info on patch and pipe do not find this info.
> I'm pretty sure there was once something in the manual about it.
`C-h i d m gnus RET i pipe RET ,'...
,----[ (info "(gnus)Saving Articles") ]
| `O p'
| `|'
| Save the current article in a pipe. Uhm, like, what I mean
| is--Pipe the current article to a process
| (`gnus-summary-pipe-output'). If given a symbolic prefix (*note
| Symbolic Prefixes::), include the complete headers in the piped
| output.
`----
As for the directory you may either use `-d' or set
`default-directory':
,----[ (info "(diff)patch Options") ]
| `-d DIRECTORY'
| `--directory=DIRECTORY'
| Make directory DIRECTORY the current directory for interpreting
| both file names in the patch file, and file names given as
| arguments to other options. *Note patch Directories::.
`----
(setq
gnus-parameters
`(;; Set default-directory for groups where patches are posted:
("emacs" (default-directory ".../emacs/lisp/"))
("auctex" (default-directory ".../auctex/"))
("gnus" (default-directory ".../gnus/lisp/"))
))
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-06-22 21:15 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 [this message]
2006-06-23 2:46 ` reader
2006-06-22 23:10 ` Steve Youngs
2006-06-23 2:50 ` reader
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=v91wtgzyck.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.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.
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).