From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patchwork is up again
Date: Tue, 23 Oct 2012 10:01:59 -0400 [thread overview]
Message-ID: <20121023140159.GA8716@denix.org> (raw)
In-Reply-To: <1564404.2akYnFFVx7@helios>
On Tue, Oct 23, 2012 at 09:59:19AM +0100, Paul Eggleton wrote:
> On Monday 22 October 2012 09:25:45 Khem Raj wrote:
> > On Sat, Oct 20, 2012 at 4:45 AM, Paul Eggleton
> > <paul.eggleton@linux.intel.com> wrote:
> > > On Friday 19 October 2012 16:37:19 Khem Raj wrote:
> > >> If you dont use patchwork dont bother but if you do then it had some
> > >> hiccups which now has been fixed hopefully. So if you dont see your
> > >> latest patch on patchwork resend it.
> > >
> > > I just sent my hddtemp patch for the third time and it still hasn't been
> > > picked up by patchwork, so I'm afraid something is still not working
> > > properly.
> >
> > we have always had issue with large patches. I dont know exact size but
> > pw did not parse large emails well. I wonder if your patch is large enough
> > to cross the bar.
>
> I've just posted v2 of the patch which is less than half the size, still no
> dice though.
>
> However, one unusual thing about this patch (and the previous version) is that
> git send-email did prompt me for an encoding, I used the default (UTF-8); even
> the subject line is encoded. Maybe patchwork doesn't understand UTF-8 - could
> that be the reason it's not being picked up?
Well, if your patch got uuencoded or base64-encoded, I'd say patchwork might
choke on it...
--
Denys
prev parent reply other threads:[~2012-10-23 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 23:37 patchwork is up again Khem Raj
2012-10-20 11:45 ` Paul Eggleton
2012-10-22 16:25 ` Khem Raj
2012-10-23 8:59 ` Paul Eggleton
2012-10-23 14:01 ` Denys Dmytriyenko [this message]
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=20121023140159.GA8716@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.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