On 7/27/05, Randy Dunlap <[email protected]> wrote:
> -Separate each logical change into its own patch.
> +Separate each _logical changes_ into its own patch.
> change
> or drop "each" and change "its own patch"
> to "a single patch file."
>
> On the other hand, if you make a single change to numerous files,
> -group those changes into a single patch. Thus a single logical change
> -is contained within a single patch.
> +group those changes into a single patch. Thus single logical changes
> +are contained within a single patch.
>
> It's better in the original form.
>
> +Do not send more than 15 patches at once to the vger mailing lists!!!
>
> Only in one place, please.
ok, here it goes agains somethig called "Affluent Albatross" aka 2.6.14-rc2-git5
-thanks-
On Mon, 26 Sep 2005, Xose Vazquez Perez wrote:
> ok, here it goes agains somethig called "Affluent Albatross" aka 2.6.14-rc2-git5
All looks good to me except for this one line:
Andrew Morton's patch scripts:
-http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.20 +http://www.zip.com.au/~akpm/linux/patches/
+Instead these ones, people should use quilt ASAP (see above).
Make that last line something like:
Instead of these (tools | scripts), quilt is the recommended
patch management tool (see above).
--
~Randy
On 9/26/05, Randy.Dunlap <[email protected]> wrote:
> All looks good to me except for this one line:
>
> Andrew Morton's patch scripts:
> -http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.20 +http://www.zip.com.au/~akpm/linux/patches/
> +Instead these ones, people should use quilt ASAP (see above).
>
> Make that last line something like:
> Instead of these (tools | scripts), quilt is the recommended
> patch management tool (see above).
ok. here it goes again.