From: Daiki Ueno <ueno@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: git am/send-email support?
Date: Thu, 29 Jan 2015 18:05:57 +0900 [thread overview]
Message-ID: <m3k306ot1m.fsf-ueno@gnu.org> (raw)
In-Reply-To: <87vbjqmiiw.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Thu, 29 Jan 2015 13:23:51 +1100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Daiki Ueno <ueno@gnu.org> writes:
>
>> Is there any Gnus command(s) to interact with git, particularly applying
>> a patch from an article buffer and composing/sending a patch by email?
>
> I haven't seen anything in particular. I just use the `|' command to
> pipe stuff into "patch"...
Thanks, I haven't thought of it. But isn't it a bit cumbersome to
manually specify the path of a git working directory (than being asked
interactively)?
I'd appreciate if anyone could provide well-tested handy little snippets
for those operations :-)
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2015-01-29 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 3:55 Daiki Ueno
2015-01-29 2:23 ` Lars Ingebrigtsen
2015-01-29 9:05 ` Daiki Ueno [this message]
2015-01-29 19:53 ` David Engster
2015-02-02 8:11 ` Daiki Ueno
2015-01-29 23:37 ` Lars Ingebrigtsen
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=m3k306ot1m.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--cc=ding@gnus.org \
--cc=larsi@gnus.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.
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).