[KJ] how to generate a multi-part patch?

[KJ] how to generate a multi-part patch?

[Robert P. J. Day]

  what's the canonical way to generate a multi-part patch?  that is,
starting from "PATCH [0/n]" and so on.  a list of bullet points will
do fine, i can take it from there.

  from what i read, i'd use quilt to generate the patch set, then
"git-send-email"?  is that it?  thanks.

rday

-- 
====================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
====================================
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

Re: [KJ] how to generate a multi-part patch?

[Ahmed S. Darwish]

On Tue, Mar 13, 2007 at 03:46:01AM -0400, Robert P. J. Day wrote:
> 
>   what's the canonical way to generate a multi-part patch?  that is,
> starting from "PATCH [0/n]" and so on.  a list of bullet points will
> do fine, i can take it from there.
>
>   from what i read, i'd use quilt to generate the patch set, then
> "git-send-email"?  is that it?  thanks.

I didn't use quilt or git-send-mail before. When I sent the array_size 
series I prepaired all the mails and put them in a =not-sent-mail mbox. 

After normally sending the first mail [00], I opened the =sent_mail mbox 
and hit reply (to let mutt put the `In-Reply-To header' automatically) 
then it's just the matter of chosing one of the not sent yet mails to 
be sent.

This way is ofcourse weak for very large patch serieses, but it just do 
the job for small sized sets ;).

Regards,

-- 
Ahmed S. Darwish
http://darwish.07.googlepages.com

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

Re: [KJ] how to generate a multi-part patch?

[Randy.Dunlap]

On Tue, 13 Mar 2007, Robert P. J. Day wrote:

>
>   what's the canonical way to generate a multi-part patch?  that is,
> starting from "PATCH [0/n]" and so on.  a list of bullet points will
> do fine, i can take it from there.
>
>   from what i read, i'd use quilt to generate the patch set, then
> "git-send-email"?  is that it?  thanks.

As usual, there isn't only one answer for this.  You can use git tools
for the patches and email, or you can use quilt tools for the patches
and email (see 'quilt mail -h').

Or you can use quilt or your own patch management for the patch
series and then use sendpatchset by Paul Jackson:
  http://www.speakeasy.org/~pj99/sgi/sendpatchset

-- 
~Randy
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

Re: [KJ] how to generate a multi-part patch?

[burns.ethan]

On Tue, Mar 13, 2007 at 03:46:01AM -0400, Robert P. J. Day wrote:
>   what's the canonical way to generate a multi-part patch?  that is,
> starting from "PATCH [0/n]" and so on.  a list of bullet points will
> do fine, i can take it from there.
>
>   from what i read, i'd use quilt to generate the patch set, then
> "git-send-email"?  is that it?  thanks.

If you make your changes in a git repo, you can always use git-format-patch to
make the patch set from a set of commits.

		--Ethan
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

Re: [KJ] how to generate a multi-part patch?

[Jesper Juhl]

On 13/03/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
>
>   what's the canonical way to generate a multi-part patch?  that is,
> starting from "PATCH [0/n]" and so on.  a list of bullet points will
> do fine, i can take it from there.
>
>   from what i read, i'd use quilt to generate the patch set, then
> "git-send-email"?  is that it?  thanks.
>
Low tech approach, but this usually works for me:

 1) Figure out the things I want to change and come up with a logical order.
 2) Make the first change and generate a diff, make next change, make
new diff etc.
 3) Start up email client, read in patch file inline, write text and
subject with PATCH [1/n], send
 4) Repeat step 3 until no more patches.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors