From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: Bjorn Helgaas <bhelgaas@google.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] PCI / ACPI: Always resume devices on ACPI wakeup notifications
Date: Thu, 28 Mar 2013 20:42:50 +0100 [thread overview]
Message-ID: <51549D3A.3000406@fold.natur.cuni.cz> (raw)
In-Reply-To: <CAErSpo4PeJFikKZQvZVTFzZDu+mA--MsgbP7WZYBdd0hJBpAow@mail.gmail.com>
Bjorn Helgaas wrote:
> On Thu, Mar 28, 2013 at 12:23 PM, Sarah Sharp
>>
>> Bjorn, I see that you're encouraging people to have their bugs and
>> symptoms in a bug tracker. I've also been doing that within Intel, in a
>> private JIRA issue tracker. I've been discussing if we can duplicate
>> some bugs or features that don't contain Intel confidential information
>> to a public JIRA at 01.org. I don't really want to use
>> bugzilla.kernel.org because, quite frankly, the interface is archaic,
>> and in the past I've gotten pushback from other devs about tracking
>> "someday" features in there.
>
> My main concern is that often there's more information relevant to a
> change than it makes sense to put in the changelog, so I like to
> include a URL to that additional info. I don't really care if that's
> for a mailing list archive, a bugzilla, a JIRA instance, etc. Issue
> trackers are more convenient than mailing lists for collecting dmesg
> logs, acpidumps, etc. The archaic bugzilla interface notwithstanding,
> I'm not sure it would be an improvement to have a collection of dozens
> of issue trackers controlled by random organizations. I'd rather have
> a single place and confidence that it will stick around.
What's wrong with bugzilla? It's nice and more appealing than Jira. From
a user perspective I always found Jira ugly. sorry to say that. ;-)
Martin
next prev parent reply other threads:[~2013-03-28 19:42 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 14:33 [PATCH] PCI / ACPI: Always resume devices on ACPI wakeup notifications Rafael J. Wysocki
2013-03-23 16:22 ` Matthew Garrett
2013-03-25 16:45 ` Sarah Sharp
2013-03-25 22:34 ` Rafael J. Wysocki
2013-03-28 12:57 ` Rafael J. Wysocki
2013-03-28 16:21 ` Bjorn Helgaas
2013-03-28 16:41 ` Rafael J. Wysocki
2013-03-28 16:46 ` Bjorn Helgaas
2013-03-28 16:59 ` Rafael J. Wysocki
2013-03-28 17:26 ` Martin Mokrejs
2013-03-28 17:49 ` Bjorn Helgaas
2013-03-28 18:23 ` Sarah Sharp
2013-03-28 19:12 ` Bjorn Helgaas
2013-03-28 19:42 ` Martin Mokrejs [this message]
2013-03-28 18:31 ` Martin Mokrejs
2013-03-28 21:27 ` Rafael J. Wysocki
2013-03-29 7:41 ` huang ying
2013-03-31 2:29 ` Martin Mokrejs
2013-03-30 2:03 ` Martin Mokrejs
2013-04-02 5:25 ` huang ying
2013-04-02 15:02 ` Martin Mokrejs
2013-04-02 16:08 ` huang ying
2013-04-02 16:53 ` Martin Mokrejs
2013-04-02 16:30 ` Bjorn Helgaas
[not found] ` <515B17D9.6030805@fold.natur.cuni.cz>
2013-04-02 20:55 ` Martin Mokrejs
2013-04-02 22:16 ` Sarah Sharp
2013-04-03 10:35 ` Martin Mokrejs
2013-04-03 2:34 ` huang ying
2013-04-03 10:39 ` Martin Mokrejs
2013-04-03 12:16 ` Martin Mokrejs
2013-04-04 11:30 ` Huang Ying
2013-04-04 19:19 ` Sarah Sharp
2013-04-05 12:30 ` Martin Mokrejs
2013-04-05 12:40 ` Martin Mokrejs
2013-04-19 23:49 ` Martin Mokrejs
2013-04-30 20:47 ` Martin Mokrejs
2013-04-02 22:49 ` Rafael J. Wysocki
2013-04-02 23:58 ` Bjorn Helgaas
2013-04-03 11:00 ` Rafael J. Wysocki
2013-04-03 2:04 ` huang ying
2013-04-03 17:29 ` Bjorn Helgaas
2013-03-30 22:38 ` [Update][PATCH] PCI / PM: Disable runtime PM of PCIe ports Rafael J. Wysocki
2013-04-01 17:34 ` Bjorn Helgaas
2013-04-01 20:51 ` Rafael J. Wysocki
2013-04-01 20:53 ` Bjorn Helgaas
2013-04-01 21:24 ` Rafael J. Wysocki
2013-04-01 23:20 ` Rafael J. Wysocki
2013-04-01 21:48 ` Martin Mokrejs
2013-04-02 5:34 ` huang ying
2013-04-02 5:28 ` huang ying
2013-04-02 5:31 ` huang ying
2013-04-03 22:34 ` Bjorn Helgaas
2013-03-28 17:10 ` [Resend][PATCH] PCI / ACPI: Always resume devices on ACPI wakeup notifications Rafael J. Wysocki
2013-03-28 21:07 ` [Update][PATCH] " Rafael J. Wysocki
2013-03-29 15:05 ` Martin Mokrejs
2013-03-29 16:05 ` Sarah Sharp
2013-03-29 17:11 ` Martin Mokrejs
2013-03-29 18:16 ` Martin Mokrejs
2013-03-29 21:37 ` Rafael J. Wysocki
2013-03-29 21:34 ` Rafael J. Wysocki
2013-04-03 22:38 ` Bjorn Helgaas
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=51549D3A.3000406@fold.natur.cuni.cz \
--to=mmokrejs@fold.natur.cuni.cz \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--cc=sarah.a.sharp@linux.intel.com \
/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.