Bug 929431 - [MINOR][PATCH] - fix man page (encfs.1) typo (it's -> its)
Summary: [MINOR][PATCH] - fix man page (encfs.1) typo (it's -> its)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fuse-encfs
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-30 14:49 UTC by Tom London
Modified: 2015-06-29 11:50 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 11:50:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
fix man page typo (it's -> its) (693 bytes, patch)
2013-03-30 14:49 UTC, Tom London
no flags Details | Diff

Description Tom London 2013-03-30 14:49:07 UTC
Created attachment 718273 [details]
fix man page typo (it's -> its)

Description of problem:
--- encfs.1	2013-03-30 07:44:37.056754757 -0700
+++ nencfs.1	2013-03-30 07:45:25.002812242 -0700
@@ -219,7 +219,7 @@
 Mount the filesystem on\-demand.  This currently only makes sense in combination
 with \fB\-\-idle\fR and \fB\-\-extpass\fR options.  When the filesystem becomes idle,
 instead of exiting, \fBEncFS\fR stops allowing access to the filesystem by
-internally dropping it's reference to it.  If someone attempts to access the
+internally dropping its reference to it.  If someone attempts to access the
 filesystem again, the extpass program is used to prompt the user for the
 password.  If this succeeds, then the filesystem becomes available again.
 .IP "\fB\-\-reverse\fR" 4


Version-Release number of selected component (if applicable):
fuse-encfs-1.7.4-11.fc19.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tom London 2013-03-30 14:56:42 UTC
Filed this upstream here: http://code.google.com/p/encfs/issues/detail?id=165

Comment 2 Fedora End Of Life 2013-09-16 13:23:46 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 3 Fedora End Of Life 2015-05-29 08:57:52 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 11:50:59 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.