Siemens GigaSet 307x isdn

Take your time. Whatever you can do to help will be welcome.

On your question about git: So far I haven't used anything but CVS on
SourceForge. I read in their newsletter that they support SVN and git now,
too, but I haven't got around to take a look yet, so I don't even know
whether our project repository might be (or easily made) accessible via
git.

In fact I would prefer using git, which I have completely switched to for
the in-kernel part of the project already. I guess I should really invest
the time for reading up on what SourceForge offers in that respect and how
I can migrate an existing project from CVS to git. But don't hold your
breath on that. For the time being, a local git-cvs tool is probably the
best way.

Thanks,
TIlman

> Is that an offer? Would you like me to assign this request to you?

That' s fine with me.

I can't promise to deliver anything at short notice. However, feel free to
prod me if this is taking too long (which it generally does once I publicly
announce something ...).

Is there a public git repository for this project or should I just use
some git-cvs tool on my side?

I really don't care about the current interface. AFAIK nothing depends on
it, so it would be quite ok with me to just replace it completely with
something more human-readable. (Provided the manpage is updated
accordingly, of course.)

Is that an offer? Would you like me to assign this request to you?

Previous comment was by me, but I forgot to log in.

> I'm moving this to Feature Requests. I'll almost certainly not find the
time to attack that in the forseeable future, but as you say, it's not
difficult, just a laborious task, so perhaps someone will volunteer.
>
> As to your question: no, changing gigacontr to textual parameters and
replies won't break the GUI tools.

Do you care about backwards compatibility? I.e., should the current,
awkward, input and/or output formats still be supported? (I do not care
about the current format. I would propose to just drop it.)

I'm moving this to Feature Requests. I'll almost certainly not find the
time to attack that in the forseeable future, but as you say, it's not
difficult, just a laborious task, so perhaps someone will volunteer.

As to your question: no, changing gigacontr to textual parameters and
replies won't break the GUI tools.
Both the command line tools (gigacontr, gigaconf) and the GUI tools
(gdemo, qgigaset) build on the library functions in the lib subdirectory of
the source tree and compiled into libgigaset.a.
So as long as the translation is done in gigacontr without touching the
library code, the GUI tools will not be affected.