linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for September 5
Date: Wed, 10 Sep 2008 06:20:07 +0400	[thread overview]
Message-ID: <48C72ED7.4000000@suse.de> (raw)
In-Reply-To: <200809100257.56108.bzolnier@gmail.com>

Hi Bartlomiej,

Bartlomiej Zolnierkiewicz wrote:
> Hi,
> 
> On Tuesday 09 September 2008, Alexey Starikovskiy wrote:
>> Hi Bartolmiej,
>>
>> This patch is really important for many people, and your report
>> blocks it from being used.
> 
> Interesting, "bad" bugreport blocks "good" patch from being used?
I am sorry if it sounds that way, your bug report is good and certainly
helps.
> 
> While the patch may be really important for some people it broke
> things here in the major way and you sent me the updated patch
> only _yesterday_.
Sorry once again to urge you.
Thanks again for both reporting bug report and testing.
Please take a look at bugs #9998, #10724, #10919 if you interested in
how important this patch is :)

Regards,
Alex.

  reply	other threads:[~2008-09-10  2:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05  9:09 linux-next: Tree for September 5 Stephen Rothwell
2008-09-05 22:47 ` Bartlomiej Zolnierkiewicz
2008-09-06  0:07   ` Andi Kleen
2008-09-08 12:39   ` Alexey Starikovskiy
2008-09-09 21:52     ` Alexey Starikovskiy
2008-09-10  0:57       ` Bartlomiej Zolnierkiewicz
2008-09-10  2:20         ` Alexey Starikovskiy [this message]
2008-09-06 16:41 ` b43 build error on m68k (was: Re: linux-next: Tree for September 5) Geert Uytterhoeven

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=48C72ED7.4000000@suse.de \
    --to=astarikovskiy@suse.de \
    --cc=bzolnier@gmail.com \
    --cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).