I'm copying my email to the bug-cssc mailing list; please copy the
mailing list when replying, since other members of the list may also
be able to help.
On Jan 5, 2008 4:43 PM, Klaus Metzger <klaus.metzger@onli...> wrote:
> James Youngman schrieb:
> > On Dec 15, 2007 2:46 PM, Klaus Metzger <klaus.metzger@onli...> wrote:
> >> Hello James,
> >> how are you?
> >> I would like to know what the status of the get -l option is you are
> >> about to develop for the CSSC?
> > I haven't worked on it.
> >> It would have been helpful for me already several times if I had had it.
> > I understand. You might want to mail the list too, in case anyone
> > else wants to help.
> > James.
> Hello James,
> no. I wanted to say that I needed it already several times, but didn't
> have it.
> Do you think you will have time sooner or later to make it?
I have been able to devote very little time to this.
Reading over the materials you sent, I note that we still need answers
to these questions from February:
<< The reason that "get -l" is not implemented at in CSSC the moment is
simply that no specification exists for the format of the output and
the Unix documentation doesn't state how the -l and -lp options
interact with the other possible options to the "get" command. For
example, what's the precise effect of "-l -e", and how does "-lp"
interact with the "-g" and "-p" options? There are likely to be
other cases where the behaviour needs to be specified, too. >>
Also, I wrote:
<< So, if you would like to document that in sufficient detail to make it
possible to implement the feature, I'm happy to write the code
implementing the options you need. >>
We still don't have any documentation for this, though. (You did
provide me with part of a Tru64 Unix manual page, but obviously the
FSF cannot distribute that, we need documentation which is not copied
or derived from that information).
Meanwhile, I'm making a start on the code. I hope you will see some
changes in the CVS tree (http://savannah.gnu.org/cvs/?group=cssc).
To finish the code changes, we need more information though. And to
make a release containing those code changes, we need documentation.