From: Segher Boessenkool <segher@kernel.crashing.org>
To: jwboyer@linux.vnet.ibm.com
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: 4xx defconfig reorg
Date: Sun, 6 Apr 2008 17:32:42 +0200 [thread overview]
Message-ID: <1d71203db510d706edf4acf1a6aa52bd@kernel.crashing.org> (raw)
In-Reply-To: <1207487181.6809.18.camel@vader.jdub.homelinux.org>
> Unless someone screams loudly and has reasons why this shouldn't go in,
These configs won't show up for "make help" anymore, which of course is
nice because that list was too long, but we need a way to get that back
since it was useful. I'll see what I can do.
Segher
next prev parent reply other threads:[~2008-04-06 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 13:06 4xx defconfig reorg Josh Boyer
2008-04-06 15:32 ` Segher Boessenkool [this message]
2008-04-07 21:36 ` Kumar Gala
2008-04-09 2:53 ` Josh Boyer
2008-04-09 6:22 ` Paul Mackerras
2008-04-09 10:56 ` Josh Boyer
2008-04-09 15:59 ` Segher Boessenkool
2008-06-18 20:36 ` 44x defconfig directory John Linn
2008-06-18 20:48 ` Sean MacLennan
2008-06-18 20:57 ` Kumar Gala
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=1d71203db510d706edf4acf1a6aa52bd@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).