Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: devzero@web.de
Cc: Neil Brown <neilb@suse.de>, NFS@lists.sourceforge.net
Subject: Re: uuid/blkid performance problem with large number of	mounts - was: Re: stale nfs file handle with exported loopback	mounts
Date: Thu, 15 Nov 2007 11:53:04 -0500	[thread overview]
Message-ID: <20071115165304.GA31958@fieldses.org> (raw)
In-Reply-To: <2086127644@web.de>

On Thu, Nov 15, 2007 at 08:54:24AM +0100, devzero@web.de wrote:
> > No one (that I know of) looks at the issue tracker on sourceforge at
> > all.
> ah -ok, sorry - i didn`t know. since there were recent  entries  from
> october, i thought it was an official way to report bugs.
> 
> > I have it on my personal "list of things to look at one day", so
> > maybe it won't get forgotten.
> thanks.  if i`m allowed to add a comment: a public bugtracker has one
> advantage: others can easily see that this or another bug exists and
> maybe they can provide (parts of) a solution or don`t need to ask for
> such.  i`m just too used to open source having open bugtrackers, so i
> thought it was the right way to go.  

The bug tracker at http://bugzilla.kernel.org/ is actually used, at
least by some people.

There's also http://bugzilla.linux-nfs.org/.  I think the kernel.org one
is probably be preferred at this point, especially for anything in a
mainstream kernel.

> if bugs not being tracked there and and you explicitly discourage
> using it - what about disabling the bugtracker entirely ?

That would make sense to me if there's an easy way to do it.

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-11-15 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  7:54 uuid/blkid performance problem with large number of mounts - was: Re: stale nfs file handle with exported loopback mounts devzero
2007-11-15 16:53 ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-15 20:07 devzero
2007-11-15 20:12 ` Trond Myklebust
2007-11-16  1:10   ` Neil Brown
2007-11-16  1:57     ` Trond Myklebust
2007-11-16  1:58       ` Trond Myklebust
2007-11-16  3:18       ` J. Bruce Fields
2007-11-16  3:24         ` Neil Brown
2007-11-13 22:44 devzero
2007-11-15  5:26 ` Neil Brown
2007-11-15 17:23   ` Trond Myklebust

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=20071115165304.GA31958@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=NFS@lists.sourceforge.net \
    --cc=devzero@web.de \
    --cc=neilb@suse.de \
    /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