Bug 762704 (GLUSTER-972)

Summary: Metabug for misc. fuse features
Product: [Community] GlusterFS Reporter: Csaba Henk <csaba>
Component: fuseAssignee: Csaba Henk <csaba>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs, tejas, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Csaba Henk 2010-06-01 22:53:00 UTC

Comment 1 Anand Avati 2010-06-07 14:35:01 UTC
PATCH: http://patches.gluster.com/patch/3367 in master (fuse: add a built-in fuse traffic dumper mechanism)

Comment 2 Tejas Bhise 2010-07-26 08:15:12 UTC
Avati, Csaba - please mark a target release on this.

Comment 3 Csaba Henk 2010-07-26 08:19:36 UTC
(In reply to comment #2)
> Avati, Csaba - please mark a target release on this.

I know now metaboogism is frowned upon. It can be closed. Is that OK?

Comment 4 Tejas Bhise 2010-07-26 09:25:23 UTC
if what was to be put in here has been put in other defects/patches then certainly this can be closed with appropriate comments.

Comment 5 Csaba Henk 2010-07-26 10:47:31 UTC
(In reply to comment #4)
> if what was to be put in here has been put in other defects/patches then
> certainly this can be closed with appropriate comments.

As a "metabug", it had no definite completion or task list or test case. The idea was that it is a bugzilla wildcard to serve as a referable entity for miscellaneous minor enhancements or tunings related to the given component (fuse). Therefore it is closeable and re-openable any time. As such practice is not encouraged, I guess the most satisfying action would be to close it terminally and forget about it.

Comment 6 Csaba Henk 2010-07-29 04:45:36 UTC
This item does not adhere to our issue tracking policy, therefore I close it as invalid.