From: maximilian attems <janitor@sternwelten.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] min/max macros from kernel.h
Date: Sun, 11 Jul 2004 10:55:25 +0000 [thread overview]
Message-ID: <20040711105525.GC1828@sputnik.stro.at> (raw)
In-Reply-To: <20040704114015.GA5381@moley.homelinux.net>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On Sat, 10 Jul 2004, Clemens Buchacher wrote:
> On Mon, Jul 05, 2004 at 04:04:00PM +0200, maximilian attems wrote:
> > please read Documentation/SubmittingPatches for further patches.
> > no attachments ;-)
>
> Thanks for the hint.
>
> > 1 patch / mail helps your patches to be merged.
>
> As these patches were interdependent and corresponded to a single
> logical change I thought it was ok to group them together as per
> paragraph 3 "Separate your changes" in Documentation/SubmittingPatches.
that's ok for experienced,
but doesn't speed up merging, as patches might need to go to different
maintainers, anyway i saw that last version touches just the header.
great continue :)
a++ maks
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-07-11 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 11:40 [Kernel-janitors] min/max macros from kernel.h Clemens Buchacher
2004-07-04 14:00 ` Michael Veeck
2004-07-05 14:04 ` maximilian attems
2004-07-10 13:53 ` Clemens Buchacher
2004-07-10 14:00 ` Clemens Buchacher
2004-07-11 10:13 ` Michael Veeck
2004-07-11 10:55 ` maximilian attems [this message]
2004-07-11 11:27 ` maximilian attems
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=20040711105525.GC1828@sputnik.stro.at \
--to=janitor@sternwelten.at \
--cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.