From: Arjan van de Ven <arjan at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH] Get rid of ncurses' TRUE and FALSE
Date: Thu, 19 Jul 2012 13:26:06 -0700 [thread overview]
Message-ID: <50086D5E.4090608@linux.intel.com> (raw)
In-Reply-To: 50086C03.4000001@linux.intel.com
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
> Please do not merge Intel's and Linaro repositories and send patches
> for what comes of it.
> If the Linaro maintainers want to do an upstream merge or if
> contributors of Linaro want to upstream
> patches they have authored then great.
> Submitting patches based on other peoples work is not agreeable to me. I
> will not take patches that
> I even suspect isn't from the original authors, and or without the
> authors consent. Do not just merge code bases
> and generate patches based on the diff, and send it to the list. They
> will not be taken.
>
specifically, I really really insist on keeping the correct authorship
information ("Author" git tag etc) for all the code going into PowerTOP.
Credit where credit is due, but also for tracking the origin and
copyright holders of the code.
next reply other threads:[~2012-07-19 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 20:26 Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-23 15:09 [Powertop] [PATCH] Get rid of ncurses' TRUE and FALSE Chris Ferron
2012-07-23 13:23 Arjan van de Ven
2012-07-23 7:48 Igor Zhbanov
2012-07-23 7:31 Magnus Fromreide
2012-07-23 6:32 Igor Zhbanov
2012-07-20 17:32 Chris Ferron
2012-07-20 7:06 Igor Zhbanov
2012-07-19 20:20 Chris Ferron
2012-07-18 22:02 Chris Ferron
2012-07-18 13:21 Igor Zhbanov
2012-07-18 13:11 Arjan van de Ven
2012-07-18 9:17 Igor Zhbanov
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=50086D5E.4090608@linux.intel.com \
--to=powertop@lists.01.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 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.