From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Wolfgang Denk <wd@denx.de>
Cc: barebox@lists.infradead.org
Subject: Re: Code "borrowed" without attribution to original authors
Date: Wed, 6 Oct 2010 05:03:24 +0200 [thread overview]
Message-ID: <20101006030324.GA32214@game.jcrosoft.org> (raw)
In-Reply-To: <20101005175354.E53D21539A0@gemini.denx.de>
On 19:53 Tue 05 Oct , Wolfgang Denk wrote:
> Dear Jean-Christophe PLAGNIOL-VILLARD,
>
> In message <20101005162019.GK25320@game.jcrosoft.org> you wrote:
> >
> > > > d424ce7 image: factorise image printing contents
> > > > 0ceafe1 Replace direct header access with the API routines
> >
> > > > aba80a2 image: rename IH_CPU to IH_ARCH to be more concistant
> > > > 7bd7d59 image: factorise string helper
> > for the record the two are not borrowed at all from U-Boot but done based on
> > barebox
>
> Oh. Interesting statement. Let me check again.
>
> Your commit:
>
> commit aba80a2d2d0f1b25185246925577ce2108247dde
> Author: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> Date: Thu Sep 23 06:48:42 2010 +0200
>
> image: rename IH_CPU to IH_ARCH to be more concistant
>
> So BB used to have IH_CPU and switched to IH_ARCH :
>
> Please compare against this U-Boot commit:
>
> commit b97a2a0a21f279d66de8a9bdbfe21920968bcb1c
> Author: Marian Balakowicz <m8@semihalf.com>
> Date: Tue Jan 8 18:14:09 2008 +0100
>
> [new uImage] Define a API for image handling operations
>
> - Add inline helper macros for basic header processing
> - Move common non inline code common/image.c
> - Replace direct header access with the API routines
> - Rename IH_CPU_* to IH_ARCH_*
>
> Signed-off-by: Marian Balakowicz <m8@semihalf.com>
>
> Pay special attention to the "Rename IH_CPU_* to IH_ARCH_*" part.
>
> Not borrowed? What an extremely unlikely coincidence then! I think
> you should try to explain that.
>
> > and as we all known the uImage format come from U-Boot I just sync it
> > recently without commit details as we do for Kconfig we do not trac
> > modifications details and we respect the copyright. SO I'll repeat myself
> > if Marian copyright is missing We will add it with pleasure.
>
>
> I recommend you to get a clue about what is needed to properly
> attribute code to the people who actually wrote it, instead of
> submitting it without any due reference and then even claiming you
> developed it yourself. I guess you are not interested in having a
> reputation as a plagiarist?
I'll repeat I'ev not borrow these two they look similar I agree but I do not
borrow them. And I'm fine to put Marian copyright I eally do not carefor the
other 2 commits. But these two I just had the same idea by looking at the
code of barebox when I was working to re-introduce the mutli-image support.
The two other commits are here for sync before finish the full sync of uImage
and I will not take Marina work as mine. I'll put my SoB as I apply it and
responsible for this integration as I did for kconfig and others without take
the copyright.
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-10-06 3:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 13:52 Wolfgang Denk
2010-10-05 16:00 ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-05 16:20 ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-05 17:53 ` Wolfgang Denk
2010-10-06 3:03 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-10-06 7:27 ` Sascha Hauer
2010-10-06 13:56 ` Wolfgang Denk
2010-10-07 7:38 ` Uwe Kleine-König
[not found] ` <20101007080810.EFDC4153A7E@gemini.denx.de>
2010-10-07 8:37 ` Uwe Kleine-König
2010-10-07 8:06 ` Sascha Hauer
2010-10-07 8:45 ` Wolfgang Denk
2010-10-07 12:45 ` Sascha Hauer
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=20101006030324.GA32214@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=wd@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