From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Tejun Heo <tj@kernel.org>
Cc: "J.H." <warthog19@eaglescrag.net>,
users@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
support@osuosl.org, Jon Tollefson <kniht@linux.vnet.ibm.com>,
Martin Bligh <mbligh@mbligh.org>,
"Jorge O. Castro" <jorge@ubuntu.com>,
bugme-admin@linux-foundation.org,
"FTPAdmin Kernel.org" <ftpadmin@kernel.org>,
Jim Zemlin <jzemlin@linux-foundation.org>
Subject: Re: [kernel.org users] [KORG] Bugzilla Upgrade / Server move
Date: Thu, 26 Mar 2009 09:04:03 +0100 [thread overview]
Message-ID: <49CB36F3.7040701@s5r6.in-berlin.de> (raw)
In-Reply-To: <49CB3356.4070104@s5r6.in-berlin.de>
Stefan Richter wrote:
> Tejun Heo wrote:
>> Is there anyway to put the comment input area at the bottom of the
>> page? Trying to reply at the top just messes up my head in weird
>> ways.
>
> Here is a patch:
> https://bugzilla.redhat.com/show_bug.cgi?id=457022#c19
PS:
Here is a 'me too' to Tejun's comment. Top-posting in bugzilla is OK if
one doesn't have to re-read the history of the bug because it's all
fresh in one's mind. This is almost only the case when one follows the
bug by mail --- but then one can also reply by mail and doesn't have a
problem with the web interface anyway. So, whenever one uses the web
interface of bugzilla.kernel.org, it is quite likely that one skims
through previous comments before adding a new one. Hence comment box
after existing comments makes much more sense, IMO. At least if
comments are shown in chronological order ( = site default).
--
Stefan Richter
-=====-=-=== -=-= -==-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2009-03-26 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 7:13 J.H.
2009-03-25 11:57 ` Alan Cox
2009-03-25 14:38 ` Martin Bligh
2009-03-25 20:21 ` [kernel.org users] " Pierre Ossman
2009-03-26 1:12 ` Dave Airlie
2009-03-26 7:11 ` Pierre Ossman
2009-03-26 7:23 ` Tejun Heo
2009-03-26 7:48 ` Stefan Richter
2009-03-26 8:04 ` Stefan Richter [this message]
2009-03-26 19:21 ` J.H.
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=49CB36F3.7040701@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=bugme-admin@linux-foundation.org \
--cc=ftpadmin@kernel.org \
--cc=jorge@ubuntu.com \
--cc=jzemlin@linux-foundation.org \
--cc=kniht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=support@osuosl.org \
--cc=tj@kernel.org \
--cc=users@kernel.org \
--cc=warthog19@eaglescrag.net \
/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
Powered by JetHome