All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: Freezing.. (was Re: Intel P6 vs P7 system call performance)
Date: Thu, 19 Dec 2002 10:39:14 -0600	[thread overview]
Message-ID: <3E01F632.1030302@inet.com> (raw)
In-Reply-To: 20021219091336.A20477@flint.arm.linux.org.uk

Russell King wrote:
> On Wed, Dec 18, 2002 at 05:08:45PM -0800, Adam J. Richter wrote:
> 
>>	I don't currently use bugzilla (just due to inertia), but the
>>whole world doesn't have to switch to something overnight in order for
>>that facility to end up saving more time and resources than it has
>>cost.  Adoption can grow gradually, and it's probably easier to work
>>out bugs (in bugzilla) and improvements that way anyhow.
> 
> 
> I'm not asking the world to switch to it overnight.  Just one person
> would be nice. 8)
> 

Ok, Russell, maybe I can lend a small hand there....

You have a bug tracking mechanism of your own on www.arm.linux.org.uk, 
along with a separate patch tracker.
Do you want ARM bug reports in bugzilla instead of your site?  If so, 
can you link to it from that bug tracker page?  (I suppose you'd want to 
  direct people to bugzilla for just 2.5.* and 2.5.*-rmk*)

I submitted a 2.4 bug to your bug tracker, got an answer to the question 
when I posted to the arm mailing lists (thanks!), and submitted a patch 
to the mailing list.  But nothing has happened on the bug status.  I 
asked if you wanted patches for bugs put in the patch tracker or the bug 
tracker, but got no reply.
I understand that you're fighting the Acorn battle of 2.5.50 -> 2.5.52, 
so I'm trying not to sound like I'm complaining.  (Failing, yes, I know, 
sorry. :/ )  Some assurance that you will acknowledge bugs in bugzilla 
would be greatly encouraging to me.  (Such as a reply to this message?)

I'll try to get 2.5 bug reports for ARM into bugzilla based on your 
comments here, but a couple of suggestions:
- post an announcement to the arm lists of where you want which bugs to go,
- link to the same in a prominent place from your bug and patch trackers
- if you can, perhaps give priority in terms of replies and such to 
those who use bugzilla... I value your replies, and if I can do 
something to increase my chances of even getting an "Ack, I'll look at 
it next week", I'll try to do that.

Comments?

Eli
--------------------. "If it ain't broke now,
Eli Carter           \                  it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------


  reply	other threads:[~2002-12-19 16:31 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  1:08 Freezing.. (was Re: Intel P6 vs P7 system call performance) Adam J. Richter
2002-12-19  9:13 ` Russell King
2002-12-19 16:39   ` Eli Carter [this message]
     [not found] <20021218161506.M7976@work.bitmover.com>
2002-12-19  0:18 ` Alan Cox
2002-12-19  0:37   ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2002-12-18 22:00 Nakajima, Jun
2002-12-18 16:41 Intel P6 vs P7 system call performance Dave Jones
2002-12-18 16:49 ` Freezing.. (was Re: Intel P6 vs P7 system call performance) Linus Torvalds
2002-12-18 16:56   ` Larry McVoy
2002-12-18 16:58   ` Dave Jones
2002-12-18 17:41     ` Linus Torvalds
2002-12-18 18:03       ` Jeff Garzik
2002-12-18 18:09         ` Mike Dresser
2002-12-23 12:34           ` Kai Henningsen
2002-12-18 19:08       ` Alan Cox
2002-12-18 19:23         ` Larry McVoy
2002-12-18 19:30           ` Alan Cox
2002-12-18 19:33             ` Larry McVoy
2002-12-18 19:42               ` Alan Cox
2002-12-18 19:45                 ` Larry McVoy
2002-12-18 20:39                   ` John Bradford
2002-12-18 22:08                     ` Larry McVoy
2002-12-18 22:37                       ` John Bradford
2002-12-19  1:09                         ` Alan Cox
2002-12-19  0:37                           ` Russell King
2002-12-19  0:58                             ` Jeff Garzik
2002-12-19  1:43                             ` Martin J. Bligh
2002-12-19 10:50                             ` Dave Jones
2002-12-19  0:59                           ` John Bradford
2002-12-19 10:27                             ` Dave Jones
2002-12-19  1:17                           ` Linus Torvalds
2002-12-19  0:08                       ` Alan Cox
2002-12-19  0:53                         ` John Bradford
2002-12-19 13:17                       ` Stephen Satchell
2002-12-19  5:34         ` Timothy D. Witham
2002-12-19  6:43           ` Andrew Morton
2002-12-19  5:45             ` Timothy D. Witham
2002-12-19  7:05           ` Martin J. Bligh
2002-12-19  6:08             ` Timothy D. Witham
2002-12-18 19:50       ` Oliver Xymoron
2002-12-18 17:06   ` Eli Carter
2002-12-18 17:08   ` Andrew Morton
2002-12-18 18:25   ` John Alvord

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=3E01F632.1030302@inet.com \
    --to=eli.carter@inet.com \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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.