From: Jeremy Kerr <jk@ozlabs.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] patchwork does not pick my patch
Date: Fri, 22 Nov 2013 07:14:31 +0800 [thread overview]
Message-ID: <528E93D7.9070708@ozlabs.org> (raw)
In-Reply-To: <528DEF38.10908@gmail.com>
Hi all,
> On 11/21/2013 12:14 PM, Masahiro Yamada wrote:
>> Hi.
>>
>> I posted a patch to change a file permission.
>> This:
>> http://lists.denx.de/pipermail/u-boot/2013-November/167573.html
>>
>> and again:
>> http://lists.denx.de/pipermail/u-boot/2013-November/167608.html
>>
>>
>> But my patch would not appear on patchwork.
>> (Maybe because there is no diff line.)
>
> I think so too. There is some handling for renames without patch in
> patchwork, but I think there is no handling for just file permission
> changes. That should be fixed in patchwork then.
Yep, that's correct - there's no support for these permission changes at
present. I'll add that!
Cheers,
Jeremy
next prev parent reply other threads:[~2013-11-21 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 11:14 [U-Boot] patchwork does not pick my patch Masahiro Yamada
2013-11-21 11:32 ` Andreas Bießmann
2013-11-21 23:14 ` Jeremy Kerr [this message]
2013-11-22 7:07 ` Masahiro Yamada
2013-11-26 1:19 ` Masahiro Yamada
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=528E93D7.9070708@ozlabs.org \
--to=jk@ozlabs.org \
--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