From: Chuck Ebbert <cebbert@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
bugme-daemon@bugzilla.kernel.org, morgoth6@gmail.com
Subject: Re: [Bugme-new] [Bug 9845] New: libata still broken for Pegasos on 2.6.24
Date: Tue, 29 Jan 2008 17:01:28 -0500 [thread overview]
Message-ID: <479FA238.5080004@redhat.com> (raw)
In-Reply-To: <20080129134214.69b7b5bc.akpm@linux-foundation.org>
On 01/29/2008 04:42 PM, Andrew Morton wrote:
>
> Gargh. How does one go from
> https://bugzilla.redhat.com/attachment.cgi?id=167747 back to the bug to
> which it is attached?
>
You can't do that because the attachments are plain text in view mode.
There is a backlink to the bug in edit mode, though:
https://bugzilla.redhat.com/attachment.cgi?id=167747&action=edit
prev parent reply other threads:[~2008-01-29 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9845-10286@http.bugzilla.kernel.org/>
2008-01-29 21:42 ` [Bugme-new] [Bug 9845] New: libata still broken for Pegasos on 2.6.24 Andrew Morton
2008-01-29 22:01 ` Chuck Ebbert [this message]
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=479FA238.5080004@redhat.com \
--to=cebbert@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=morgoth6@gmail.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 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).