From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/9] Clean up top-level directory structure
Date: Thu, 09 Jul 2009 14:31:59 -0500 [thread overview]
Message-ID: <1247167919.905.50.camel@localhost.localdomain> (raw)
In-Reply-To: <200907091515.44039.vapier@gentoo.org>
On Thu, 2009-07-09 at 15:15 -0400, Mike Frysinger wrote:
> On Thursday 09 July 2009 14:49:07 Peter Tyser wrote:
> > > > Move lib_ppc to lib/ppc
> > > > Move lib_arm to lib/arm
> > > > Move lib_i386 to lib/i386
> > > > Move lib_m68k to lib/m68k
> > > > Move remaining lib_<ARCH> to lib/<ARCH>
> > >
> > > why is ppc/arm/i386/m68k special ? seems like it'd make more sense to
> > > either have one patch for every arch or squash them altogether. a squash
> > > here sounds ok to me.
> >
> > I originally didn't squash them all together because of the 100KB
> > mailing list limit. It looked like I'd need to only use 1 line of patch
> > context to get the lib_<arch> changes to be < 100KB, so I split them up
> > instead.
> >
> > I originally was going to do each arch independently, but realized there
> > was no real significant change for avr32, blackfin, mips, nios, nios2,
> > and sparc so I squashed them together.
>
> since it's pretty much all renames, i would have thought git-format-patch with
> the -M option would produce a summary that is under 100kB ?
Without the -M option the patches were hundreds of KB, with -M and only
2 lines of context they are still pretty large (as sent to the mailing
list):
55K 0002-Move-lib_ppc-to-lib-ppc.patch
7.2K 0003-Move-lib_arm-to-lib-arm.patch
6.7K 0004-Move-lib_i386-to-lib-i386.patch
16K 0005-Move-lib_m68k-to-lib-m68k.patch
20K 0006-Move-remaining-lib_-ARCH-to-lib-ARCH.patch
98K 0007-Move-lib_generic-to-lib-generic.patch
> > Anyway, that's the logic, I can resubmit if necessary. Or the arch
> > changes can be squashed together by whoever pushes the changes to get
> > around the mailing list limit.
>
> up to Wolfgang how he wants it
Wolfgang, let me know if you want this series reorganized.
Best,
Peter
next prev parent reply other threads:[~2009-07-09 19:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 15:08 [U-Boot] [PATCH 0/9] Clean up top-level directory structure Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 1/9] Move architecture specific config.mk files into subdirs Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 2/9] Move lib_ppc to lib/ppc Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 3/9] Move lib_arm to lib/arm Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 4/9] Move lib_i386 to lib/i386 Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 5/9] Move lib_m68k to lib/m68k Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 6/9] Move remaining lib_<ARCH> to lib/<ARCH> Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 7/9] Move lib_generic to lib/generic Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 8/9] Move libfdt to lib/libfdt Peter Tyser
2009-07-09 15:08 ` [U-Boot] [PATCH 9/9] Move api_examples to api/examples Peter Tyser
2009-07-09 16:22 ` Rafal Jaworowski
2009-07-09 16:36 ` Peter Tyser
2009-07-09 20:07 ` Wolfgang Denk
2009-07-10 13:22 ` Rafal Jaworowski
2009-07-09 17:57 ` [U-Boot] [PATCH 0/9] Clean up top-level directory structure Mike Frysinger
2009-07-09 18:49 ` Peter Tyser
2009-07-09 19:15 ` Mike Frysinger
2009-07-09 19:31 ` Peter Tyser [this message]
2009-07-09 20:20 ` Wolfgang Denk
2009-07-09 20:25 ` Peter Tyser
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=1247167919.905.50.camel@localhost.localdomain \
--to=ptyser@xes-inc.com \
--cc=u-boot@lists.denx.de \
/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.