From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uboot-tools: fix license issues
Date: Sat, 2 Nov 2013 18:38:53 +0100 [thread overview]
Message-ID: <20131102183853.34b34d7d@skate> (raw)
In-Reply-To: <20131102173258.GC3542@free.fr>
Dear Yann E. MORIN,
On Sat, 2 Nov 2013 18:32:58 +0100, Yann E. MORIN wrote:
> On 2013-11-02 17:43 +0100, Thomas Petazzoni spake thusly:
> > However, a patch not committed and not visible in patchwork is a bit
> > weird (except for patches that only rename files, because the patch
> > contents are empty and patchwork doesn't understand that).
>
> Actually, this last part is now wrong: patchwork should now recognise
> renames-only patches (since about two weeks now).
Aaah, and this is actually true! The ngrep patches renaming patch was
recognized by patchwork.
My bad,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-02 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 16:46 [Buildroot] [PATCH] uboot-tools: fix license issues Gustavo Zacarias
2013-11-02 13:43 ` Thomas Petazzoni
2013-11-02 16:24 ` Gustavo Zacarias
2013-11-02 16:43 ` Thomas Petazzoni
2013-11-02 17:32 ` Yann E. MORIN
2013-11-02 17:38 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-22 14:37 Gustavo Zacarias
2013-10-22 14:57 ` Thomas De Schampheleire
2013-10-22 15:22 ` Gustavo Zacarias
2013-10-23 9:39 ` Thomas Petazzoni
2013-10-24 6:51 ` Thomas De Schampheleire
2013-10-24 8:20 ` Luca Ceresoli
2013-10-24 12:24 ` Arnout Vandecappelle
2013-10-24 12:35 ` Gustavo Zacarias
2013-10-24 19:29 ` Arnout Vandecappelle
2013-10-22 16:39 ` Peter Korsgaard
2013-10-22 16:39 ` Gustavo Zacarias
2013-10-22 17:01 ` Thomas De Schampheleire
2013-10-22 17:49 ` Peter Korsgaard
2013-10-22 17:50 ` Gustavo Zacarias
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=20131102183853.34b34d7d@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.