All of lore.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: Neil Brown <neilb@suse.de>, Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: bfields@fieldses.org, 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 21:07:20 +0100	[thread overview]
Message-ID: <2087477778@web.de> (raw)

> Is it possible to turn this feature off on sourceforge? I

yes - iirc, i have seen projects without  a tracker or without other option=
, being on by default.

if you want to disable it, maybe this one helps:

https://sourceforge.net/docs/G03/en/#tracker

Tracker

Trackers may be flagged as hidden by project administrators. No means is pr=
ovided to completely remove a Tracker. All data will be preserved within hi=
dden Trackers, but it will not be accessible by site users.

To hide a Tracker as a project administrator:

   1. Click on the "Tracker" link for the project.
   2. Click on the "Admin" link.
   3. Click on the name of the desired Tracker.
   4. Click on the "Update Preferences" link.
   5. Change the "Visibility of this Tracker" pulldown menu value as desire=
d. Default is "Visible to all site users". A change to "Visible to project =
members only" will restrict view of the Tracker to members of your project =
team. A change to "Not visible (hidden)" will prevent view of the Tracker b=
y any site user, including members of your project team; only Tracker admin=
s and project admins will then be able to see this Tracker when in the admi=
n view.
   6. Click on the "SUBMIT" button to complete the change.

Tracker items may be removed by SourceForge.net staff, if given suitable re=
ason. The "Deleted" Tracker item "Status" value does not actually delete Tr=
acker items or remove them from view; this status option is provided for so=
rting purposes. No means is provided for project administrators and site us=
ers to remove Tracker items on their own. If you need a Tracker item remove=
d, please contact the SourceForge.net team. Similar is true of comments on =
Tracker items.

regards
roland


> -----Urspr=FCngliche Nachricht-----
> Von: "Trond Myklebust" <trond.myklebust@fys.uio.no>
> Gesendet: 15.11.07 18:24:24
> An: Neil Brown <neilb@suse.de>
> CC: bfields@fieldses.org, NFS@lists.sourceforge.net
> Betreff: Re: [NFS] uuid/blkid performance problem with large number of mo=
unts - was: Re:  stale nfs file handle with exported loopback mounts


> =

> =

> On Thu, 2007-11-15 at 16:26 +1100, Neil Brown wrote:
> > On Tuesday November 13, devzero@web.de wrote:
> > > since i posted 2 problems in one mail - and one problem is solved now=
, for the second problem i have opened a ticket at =

> > > =

> > > http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1831403&=
group_id=3D14&atid=3D100014  =

> > > ( uuid/blkid performance problem with large number of mounts )
> > > =

> > > so this won`t get lost.
> > =

> > Unfortuantely that is a bit like saying "I've placed in the nice round
> > filling cabinet so it won't get lost", not realising that the nice
> > round filing cabinet is actually a garbage be.
> > =

> > No one (that I know of) looks at the issue tracker on sourceforge at
> > all.
> > =

> > I have it on my personal "list of things to look at one day", so maybe
> > it won't get forgotten.
> =

> Is it possible to turn this feature off on sourceforge? It is rather
> unfortunate that people take the time to type these things up, without
> realising that the tracker is unmonitored. It would be even better if we
> could display a message saying "please submit this to the mailing lists
> and/or bugzilla".
> =

> Cheers
>   Trond
> =

> =



___________________________________________________________________________=
___
Jetzt neu! Im riesigen WEB.DE Club SmartDrive Dateien freigeben und mit =

Freunden teilen! http://www.freemail.web.de/club/smartdrive_ttc.htm/?mc=3D0=
21134


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-11-15 20:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 20:07 devzero [this message]
2007-11-15 20:12 ` uuid/blkid performance problem with large number of mounts - was: Re: stale nfs file handle with exported loopback mounts 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
  -- strict thread matches above, loose matches on Subject: below --
2007-11-15  7:54 devzero
2007-11-15 16:53 ` J. Bruce Fields
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=2087477778@web.de \
    --to=devzero@web.de \
    --cc=NFS@lists.sourceforge.net \
    --cc=bfields@fieldses.org \
    --cc=neilb@suse.de \
    --cc=trond.myklebust@fys.uio.no \
    /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.