From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/75092 Path: news.gmane.org!not-for-mail From: Francis Moreau Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: Sending patch with Gnus Date: Thu, 16 Dec 2010 11:01:10 +0100 Message-ID: References: <871v5i212s.fsf@tux.homenetwork> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1292493741 7408 80.91.229.12 (16 Dec 2010 10:02:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 16 Dec 2010 10:02:21 +0000 (UTC) Cc: emacs-devel@gnu.org, ding@gnus.org, Thierry Volpiatto To: Leo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 16 11:02:14 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PTAf3-0005l7-Uy for ged-emacs-devel@m.gmane.org; Thu, 16 Dec 2010 11:02:12 +0100 Original-Received: from localhost ([127.0.0.1]:59014 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PTAes-0000t4-Oy for ged-emacs-devel@m.gmane.org; Thu, 16 Dec 2010 05:01:58 -0500 Original-Received: from [140.186.70.92] (port=57568 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PTAeE-0000er-PG for emacs-devel@gnu.org; Thu, 16 Dec 2010 05:01:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PTAeC-00031v-Ou for emacs-devel@gnu.org; Thu, 16 Dec 2010 05:01:18 -0500 Original-Received: from mail-wy0-f169.google.com ([74.125.82.169]:32952) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PTAeC-00031k-JK for emacs-devel@gnu.org; Thu, 16 Dec 2010 05:01:16 -0500 Original-Received: by wyj26 with SMTP id 26so2416807wyj.0 for ; Thu, 16 Dec 2010 02:01:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :date:in-reply-to:message-id:user-agent:mime-version:content-type; bh=14yVt/VuOsomPLvBsqn0VpwCtDwevn5ebEcdiIPNRPQ=; b=XU7dgIRcdQVx1DbpE9rOQN2Dbj1KnHhoPkXeNE89v4dYHMYw3n1gaDL17a181YSIwn d2Ts8qn1wl7jIubQ2Ekhc9z8o0EO4CaLFnlkoE4ZO9WyTMArZ6n8gCzLrlCM2jp35IN/ bozLYCEl+PEtUr5yJ8KBbHyrMRxuUtjUrKKb8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=cqlhWQszwQOWYHPaIP3vK3+EFzjSq/+pfSqR2VWEkq10iJ1ba9TtnnPLrx8x10d18c c1G3ee36Yrd6ubms6ENm+EyeuqiX8juwprWPRMPozeBr0aM6qjKx3GrpLCXGMWlLXV1C WHW8RkWMZif4341o8uH/4FN7z9pUMXMvC6o+c= Original-Received: by 10.227.151.202 with SMTP id d10mr2541403wbw.0.1292493675705; Thu, 16 Dec 2010 02:01:15 -0800 (PST) Original-Received: from localhost (au213-1-82-235-205-153.fbx.proxad.net [82.235.205.153]) by mx.google.com with ESMTPS id q18sm287412wbe.5.2010.12.16.02.01.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 16 Dec 2010 02:01:14 -0800 (PST) In-Reply-To: (Leo's message of "Thu, 16 Dec 2010 06:09:34 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:133738 gmane.emacs.gnus.general:75092 Archived-At: Leo writes: [...] > > I tweaked gnus-dired to support git-send-email (patches attached). Thanks for doing that. Unfortunately your patches don't seem to be based on Gnus repository but rather to emacs one that I don't have. So I can't test them. > So if you have gnus-dired loaded you can in dired buffer: > > C-c C-m C-i import patches as DRAFTS > C-c C-m C-s send patches directly > > This is handy when you need to send a large patch set. For one to two > patches I just copy and paste. Funny because I feel the opposite, I use git-send-email(1) when dealing with a large patch set since the overhead to set it up is ok in this case. But for one patch, I do it by hands as you do, but I would prefer to not have editing the email manually. But I think, your approach can still be usefull since it imports patches as _drafts_. I don't think it's a good idea to modify the patch itself, but modifying or adding some header fields like To, Cc, Bcc... should be ok. And I like to check what the patch looks like before sending it. One other idea is to generate one or several drafts from a buffer which contains one or several mbox files. Let's call the magic command: M-x create-draft-from-buffer (yeah the name sucks). With such command, one could do in an emacs session: M-! git format-patch --stdout HEAD~4 C-x o M-x create-draft-from-buffer So you're putting in the *Shell Command Output* buffer the mbox files, and then switching to that buffer and generating the drafts. The main advantages I see is that you use a shell command to generate the buffer containing the patches. BTW, if you needn't to modify the patches and only want to see them before sending them then you can currently do this: M-! git format-patch --stdout HEAD~4 >/tmp/patch-set.mbox C-x b *Group* G f /tmp/patch-set.mbox This will create a nndoc group which contains all your patches as articles. Then you can mark all of them and resend them with 'S D r'. But you can't add Cc or Gcc header fields with this method. -- Francis