From: Tomas Szepe <szepe@pinerecords.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: jgarzik@pobox.com, zaitcev@redhat.com, davem@redhat.com,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, netfilter-devel@lists.samba.org,
phillim2@comcast.net, rmk@arm.linux.org.uk
Subject: Re: [PATCHSET] Multiarch kconfig cleanup
Date: Thu, 2 Jan 2003 22:31:55 +0100 [thread overview]
Message-ID: <20030102213155.GF17053@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301021152350.3665-100000@home.transmeta.com>
> [torvalds@transmeta.com]
>
> > This is the first time I'm trying to get more than 3 people to work
> > together so I'd be grateful if you didn't kick me too hard should I have
> > screwed up.
>
> I'd really like to see the organizational patches first (ie the
> net/Kconfig type of changes), and leave the "conditional menu" patches for
> later, especially as they would seem to be improved by an extension to the
> config language (ie the "menucond" thing).
>
> Also, I don't fetch patches, I'd much rather just be mailbombed.
In a minute, I'm sending the organizational stuff rediffed,
that's patches 15-36 from the original batch as 1-22. I'll
only send to Linus & CC lkml.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-01-02 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 18:20 [PATCHSET] Multiarch kconfig cleanup Tomas Szepe
2003-01-02 19:54 ` Linus Torvalds
2003-01-02 21:31 ` Tomas Szepe
2003-01-02 21:31 ` Tomas Szepe [this message]
2003-01-02 19:54 ` Linus Torvalds
2003-01-02 23:05 ` Geert Uytterhoeven
2003-01-02 23:05 ` Geert Uytterhoeven
2003-01-02 23:10 ` Jeff Garzik
2003-01-04 20:24 ` Geert Uytterhoeven
2003-01-04 22:39 ` Alan Cox
2003-01-04 22:11 ` Geert Uytterhoeven
2003-01-04 23:46 ` Alan Cox
2003-01-02 23:10 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 18:20 Tomas Szepe
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=20030102213155.GF17053@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=netfilter-devel@lists.samba.org \
--cc=phillim2@comcast.net \
--cc=rmk@arm.linux.org.uk \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zaitcev@redhat.com \
/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.