From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Too Large patch
Date: Tue, 30 Dec 2008 11:47:13 +0100 [thread overview]
Message-ID: <20081230104713.9868E833DBB7@gemini.denx.de> (raw)
In-Reply-To: <200812300317.55242.vapier@gentoo.org>
Dear Mike Frysinger,
In message <200812300317.55242.vapier@gentoo.org> you wrote:
>
> > I have a rather large patch that really is just one change just to a lot
> > of files so I do not want to split it up.
> >
> > What to do ?? It got rejected by the mail administrator.
>
> summarize the change and then compress & attach
NO!!! Please read the instructions before making fals recommendations.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"The one charm of marriage is that it makes a life of deception a
neccessity." - Oscar Wilde
next prev parent reply other threads:[~2008-12-30 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 8:08 [U-Boot] Too Large patch kenneth johansson
2008-12-30 8:17 ` Mike Frysinger
2008-12-30 10:47 ` Wolfgang Denk [this message]
2008-12-30 11:44 ` Mike Frysinger
2008-12-30 14:54 ` Wolfgang Denk
2008-12-30 20:21 ` Mike Frysinger
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=20081230104713.9868E833DBB7@gemini.denx.de \
--to=wd@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox