From: "Tomas Winkler" <tomasw@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: holtmann@linux.intel.com, linville@tuxdriver.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-08-26
Date: Wed, 27 Aug 2008 14:42:43 +0300 [thread overview]
Message-ID: <1ba2fa240808270442k20f70e69n6a6203d236376f5@mail.gmail.com> (raw)
In-Reply-To: <20080827.033237.236091327.davem@davemloft.net>
On Wed, Aug 27, 2008 at 1:32 PM, David Miller <davem@davemloft.net> wrote:
> From: "Tomas Winkler" <tomasw@gmail.com>
> Date: Wed, 27 Aug 2008 13:05:23 +0300
>
>> There is a central problem here, since I cannot really adjust driver
>> development progress from obvious reason with Linux merging window.
>
> Indeed, that's exactly what your core problem is.
>
> You think it's OK to contaminate upstream just because of the
> way you have choosen to maintain your driver.
>
I don't think I contaminate upstream I'm just trying to fix bugs so
people can work with the HW.
> Well guess what, it's not OK to do that, and it's absolutely not our
> problem that you choose to do your development in the most anti-social
> way possible wrt. upstream.
>
> Anyways, keep defending yourself.
I'm not defending myself I'm explaining myself.
> If you persist, I can certainly make things _really_ easy, such that
> if there isn't a regression list entry for the bug you are fixing and
> it isn't mentioned explicitly in your commit message, I simply will
> refuse to take your changes outside of the merge window.
>
> It's that simple.
>
> Would you like things to work that way, where I'm a hard ass, or would
> you like to stop defending yourself endlessly, and instead start to be
> reasonable?
I'm not sure why you are so militant, you cut out form my email sentences
like 'Yes' and 'Understood'
Is this personal ?
Tomas
next prev parent reply other threads:[~2008-08-27 11:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 1:30 John W. Linville
2008-08-27 7:38 ` Tomas Winkler
2008-08-27 8:40 ` David Miller
2008-08-27 9:13 ` Tomas Winkler
2008-08-27 11:10 ` Marcel Holtmann
2008-08-27 10:05 ` Tomas Winkler
2008-08-27 10:10 ` Johannes Berg
2008-08-27 10:33 ` David Miller
2008-08-27 11:34 ` Tomas Winkler
2008-08-27 11:45 ` David Miller
2008-08-27 12:26 ` Tomas Winkler
2008-08-27 13:10 ` Michael Buesch
2008-08-27 14:55 ` Tomas Winkler
2008-08-27 15:22 ` Michael Buesch
2008-08-27 15:45 ` Tomas Winkler
2008-08-27 10:32 ` David Miller
2008-08-27 11:42 ` Tomas Winkler [this message]
2008-08-27 13:57 ` Arjan van de Ven
2008-08-27 11:39 ` David Miller
2008-08-27 19:26 ` Tomas Winkler
2008-08-27 20:25 ` Michael Buesch
2008-08-27 23:11 ` Tomas Winkler
2008-08-27 23:31 ` Luis R. Rodriguez
2008-08-28 0:19 ` Tomas Winkler
2008-08-28 1:30 ` Luis R. Rodriguez
2008-08-28 7:59 ` Tomas Winkler
2008-08-28 10:35 ` Bruno Randolf
2008-08-28 10:52 ` Tomas Winkler
2008-08-28 11:13 ` Bruno Randolf
2008-08-28 8:31 ` Michael Buesch
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=1ba2fa240808270442k20f70e69n6a6203d236376f5@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=davem@davemloft.net \
--cc=holtmann@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®