Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	David Miller <davem@davemloft.net>,
	torvalds@linux-foundation.org, linville@tuxdriver.com,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344
Date: Tue, 03 Nov 2009 09:31:01 +0100	[thread overview]
Message-ID: <1257237061.28469.43.camel@johannes.local> (raw)
In-Reply-To: <20091103082201.GG3212@core.coreip.homeip.net>

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On Tue, 2009-11-03 at 00:22 -0800, Dmitry Torokhov wrote:

> I do not understand what the fuss is about. We are pretty far in release
> process (rc6 is about to be cut I'd expect) and we have an issue that
> for all practical purposes kills the box on resume. Yes, I want action
> to be swift in this case and (unless author or maintainer - who were
> CCed on the email - have otehr solutiuon) the offending commit to be
> reverted. If it was rc1 or rc2 or 3 I'd feel differently.

Oh, I don't disagree that swift action is good.

I just think that it's a matter of courtesy that should be independent
from the release cycle to ask the author/maintainer by default, not as a
second thought ("unless [...] have other solution"). You can always CC
Linus and ask him to revert if you don't get a response.

What's wrong with that? It doesn't actually delay the action, but it
makes the discussion much more friendly and cooperative instead of
giving the author and maintainer the feeling that their opinion only
matters as a second thought.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-11-03  8:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  5:31 Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344 Dmitry Torokhov
2009-11-03  6:49 ` David Miller
2009-11-03  6:52   ` Dmitry Torokhov
2009-11-03  7:16     ` Marcel Holtmann
2009-11-03  7:44       ` Johannes Berg
2009-11-03  8:22         ` Dmitry Torokhov
2009-11-03  8:31           ` Johannes Berg [this message]
2009-11-03  8:47             ` Dmitry Torokhov
2009-11-03  8:57               ` Johannes Berg
2009-11-03 15:29                 ` Marcel Holtmann
2009-11-03 15:38                   ` Linus Torvalds
2009-11-05 19:19                   ` Pavel Machek
2009-11-03 15:31         ` Linus Torvalds
2009-11-04  6:34         ` Andrew Morton
2009-11-04  8:41           ` David Miller
2009-11-04 15:23             ` Andrew Morton
2009-11-04 16:32               ` David Miller
2009-11-03 15:26       ` Linus Torvalds
2009-11-03 15:36         ` Marcel Holtmann
2009-11-03 15:43           ` Linus Torvalds
2009-11-03 16:07             ` Linus Torvalds
2009-11-03 16:08             ` Marcel Holtmann
2009-11-03 16:23               ` Linus Torvalds
2009-11-03 16:37                 ` Linus Torvalds
2009-11-03 16:44                 ` Marcel Holtmann
2009-11-03 16:59                   ` Linus Torvalds
2009-11-03 16:29               ` Ingo Molnar
2009-11-03 16:49                 ` Marcel Holtmann
2009-11-03 17:04                   ` Ingo Molnar
2009-11-03 17:24                 ` Luis R. Rodriguez
2009-11-03 17:37                   ` Linus Torvalds
2009-11-03 17:49                     ` Dmitry Torokhov
2009-11-03 17:55                     ` Luis R. Rodriguez
2009-11-03 15:54           ` Zdenek Kabelac

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=1257237061.28469.43.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=marcel@holtmann.org \
    --cc=torvalds@linux-foundation.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