git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Add script for patch submission via e-mail.
Date: Tue, 5 Jul 2005 11:34:41 +0200	[thread overview]
Message-ID: <20050705093441.GD6191@pasky.ji.cz> (raw)
In-Reply-To: <7vll5h7k5t.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Sat, Jun 11, 2005 at 03:32:30AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> This git-format-patch-script is what I use to prepare patches
> for e-mail submission.
> 
> Typical usage is:
> 
> $ git-format-patch-script -B -C --find-copies-harder HEAD linus
> 
> to prepare each commit with its patch since "HEAD" forked from
> "linus", one file per patch for e-mail submission.  Each output
> file is numbered sequentially from 1, and uses the first line of
> the commit message (massaged for pathname safety) as the
> filename.
> 
> $ git-format-patch-script -B -C --find-copies-harder HEAD linus .patch/
> 
> creates output files in .patch/ directory.
> 
> Signed-off-by: Junio C Hamano <junkio@cox.net>
> ---
> *** Linus I am submitting this one because some patches on
> *** read-tree I am going to send you will need this for
> *** formatting into a form that is easier to review.  And this
> *** in turn can use diff-tree --find-copies-harder, which I
> *** indeed used to generate the patches that follow.

Any reason why this was not applied? It appears kind of cool. Well, I
will probably take it and extend cg-mkpatch with it so I don't need it
in Git, but I'm so altruistic and want to bring at least a bit of light
to the gloomy dark world of the poor core Git plumbing users.  ;-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
<Espy> be careful, some twit might quote you out of context..

  reply	other threads:[~2005-07-05  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-11  1:32 [PATCH] Add script for patch submission via e-mail Junio C Hamano
2005-07-05  9:34 ` Petr Baudis [this message]
2005-07-05  9:39   ` Jon Seymour
2005-07-05 15:20   ` Junio C Hamano
2005-07-05 16:18     ` Jon Seymour
2005-07-05 20:19   ` 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=20050705093441.GD6191@pasky.ji.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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).