VikingExtractor needs man page
Bug #816793 reported by
Kip Warner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Avaneya | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
Medium
|
Joe Tang |
Bug Description
The viking-extractor(1) tool needs a man page now that its interface has stabilized. The suggested location in the source tree is here:
<Avaneya/
The information that should be available in the man page can be found in the ShowHelp() function contained in the source:
Changed in avaneya: | |
status: | New → Incomplete |
description: | updated |
summary: |
- VikingExtractor needs info / man page + VikingExtractor needs man page |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
To post a comment you must log in.
Hey, Kip, just curious about this:
"> The viking-extractor tool needs an info and man page created for it as> soon as its interface is stabilized."
What is the Viking-Extractor tool? I'll need to try it out or use/see it in order to provide information, heh.Thanks in advance.
> Date: Wed, 27 Jul 2011 05:03:08 +0000 /bugs.launchpad .net/bugs/ 816793 /bugs.launchpad .net/avaneya/ +bug/816793/ +subscriptions
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 816793] Re: VikingExtractor needs info / man page
>
> ** Changed in: avaneya
> Status: New => Incomplete
>
> ** Also affects: avaneya/trunk
> Importance: Low
> Assignee: Wolfos (one-grey-wing)
> Status: Incomplete
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> VikingExtractor needs info / man page
>
> Status in Avaneya:
> Incomplete
> Status in Avaneya trunk series:
> Incomplete
>
> Bug description:
> The viking-extractor tool needs an info and man page created for it as
> soon as its interface is stabilized.
>
> To manage notifications about this bug go to:
> https:/