On 5 Oct 2002, Maksim (Max) Krasnyanskiy wrote:
> You can either pull all of them from:
Ok, pulled. But _please_ do this the regular way next time. There's even a
script to help you do it in linux/Documentation/BK-usage/bk-mak-sum, which
does it all for you for BK patches.
(many people end up doing their own thing, you don't have to use that
particular script, of course. But the important thing I want is that the
_email_ should contain enough information to make a good first pass
judgement on what the patch does, and in particular it is important for me
to see what a "bk pull" will actually change.)
That's why the "diffstat" is important to me if I do a BK pull - and why I
want to see the patches as plaintext if I apply stuff to generic files..
- if you use BK (which is great - your tree looked fine and the only real
problem was that I had to verify it separately by hand first), please
send one email for the "bk pull", and include a diffstat for the whole
thing in that one email.
- if you use patches, please send them as clear-text in the email itself,
and don't think that I want to go fetch them separately from some other
For optimal exposure, do both - this is what Greg KH does for USB stuff
(he sends the BK email to me and to the kernel list, and sends individual
patches to the kernel list only). Which really helps the people who don't
want to use BK for some reason.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:52 EST