5:29 p.m.
Hi,
Arne Jørgensen wrote improved completing support for inserting stuff
like "\usepackage[bar,baz,zab]{foo}" in AUCTeX. The function needs
`completing-read-multiple' from `crm.el'[1] which is available in
Emacs 21 and Emacs 22 (CVS[2]), but not in XEmacs.
We found that `riece.el'[3] which is available as an XEmacs package
seems to duplicate some code from `crm.el' for XEmacs.
Wouldn't it make much more sense to include `crm.el' in `xemacs-base',
some utility package or distribute it as a separate package instead of
duplicating it's code in several packages?
Bye, Reiner.
[1]
;;; crm.el --- read multiple strings with completion
;; Copyright (C) 1985, 1986, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
;; 2000, 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
;; Author: Sen Nagata <sen(a)eccosys.com>
;; Keywords: completion, minibuffer, multiple elements
[2]
http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/emacs/emacs/lisp/emacs...
[3] Cc-ing the author of riece: Daiki Ueno
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
11:51 a.m.
>>>> "Reiner" == Reiner Steib
<reinersteib+gmane(a)imap.cc> writes:
Hi,
Arne Jørgensen wrote improved completing support for inserting
stuff like "\usepackage[bar,baz,zab]{foo}" in AUCTeX. The
function needs `completing-read-multiple' from `crm.el'[1] which
is available in Emacs 21 and Emacs 22 (CVS[2]), but not in
XEmacs.
We found that `riece.el'[3] which is available as an XEmacs
package seems to duplicate some code from `crm.el' for XEmacs.
Wouldn't it make much more sense to include `crm.el' in
`xemacs-base', some utility package or distribute it as a
separate package instead of duplicating it's code in several
packages?
Bye, Reiner.
I support this proposal. In the coming days I am going to try to sync
the latest official Auctex release with the official xemacs pkg, and I
think it would be a good idea if any extern code which is required for
auctex to work, is as uniform as possible.
Uwe Brauer
12:44 p.m.
New subject: crm.el (completing-read-multiple) in XEmacs (was: cmr.el (completing-read-multiple) in XEmacs)
On Thu, Oct 13 2005, Uwe Brauer wrote:
>>>>> "Reiner" == Reiner Steib
<reinersteib+gmane(a)imap.cc> writes:
> Arne Jørgensen wrote improved completing support for inserting
> stuff like "\usepackage[bar,baz,zab]{foo}" in AUCTeX. The
> function needs `completing-read-multiple' from `crm.el'[1] which
> is available in Emacs 21 and Emacs 22 (CVS[2]), but not in
> XEmacs.
> We found that `riece.el'[3] which is available as an XEmacs
> package seems to duplicate some code from `crm.el' for XEmacs.
> Wouldn't it make much more sense to include `crm.el' in
> `xemacs-base', some utility package or distribute it as a
> separate package instead of duplicating it's code in several
> packages?
I support this proposal. [...]
Can we expect _any_ reaction (yes, no, maybe) from the XEmacs board?
Am I posting to the wrong list? Which would be more appropriate?
Bye, Reiner.
PS: Sorry for the typo in the original subject.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
12:15 a.m.
New subject: crm.el (completing-read-multiple) in XEmacs
Reiner Steib wrote:
On Thu, Oct 13 2005, Uwe Brauer wrote:
>>>>>>"Reiner" == Reiner Steib
<reinersteib+gmane(a)imap.cc> writes:
>>>>>>
>>>>>>
> > Arne Jørgensen wrote improved completing support for inserting
> > stuff like "\usepackage[bar,baz,zab]{foo}" in AUCTeX. The
> > function needs `completing-read-multiple' from `crm.el'[1] which
> > is available in Emacs 21 and Emacs 22 (CVS[2]), but not in
> > XEmacs.
>
> > We found that `riece.el'[3] which is available as an XEmacs
> > package seems to duplicate some code from `crm.el' for XEmacs.
>
> > Wouldn't it make much more sense to include `crm.el' in
> > `xemacs-base', some utility package or distribute it as a
> > separate package instead of duplicating it's code in several
> > packages?
>
>I support this proposal. [...]
>
>
Can we expect _any_ reaction (yes, no, maybe) from the XEmacs board?
Am I posting to the wrong list? Which would be more appropriate?
Bye, Reiner.
i think this sounds great. probably crm.el should go in edit-utils.
does this need to be ported or does it work already under xemacs?
10:34 a.m.
New subject: crm.el (completing-read-multiple) in XEmacs
On Sun, Oct 23 2005, Ben Wing wrote:
>>>>>>>"Reiner" == Reiner Steib
<reinersteib+gmane(a)imap.cc> writes:
>> > Arne Jørgensen wrote improved completing support for inserting
>> > stuff like "\usepackage[bar,baz,zab]{foo}" in AUCTeX. The
>> > function needs `completing-read-multiple' from `crm.el'[1] which
>> > is available in Emacs 21 and Emacs 22 (CVS[2]), but not in
>> > XEmacs.
>>
>> > We found that `riece.el'[3] which is available as an XEmacs
>> > package seems to duplicate some code from `crm.el' for XEmacs.
>>
>> > Wouldn't it make much more sense to include `crm.el' in
>> > `xemacs-base', some utility package or distribute it as a
>> > separate package instead of duplicating it's code in several
>> > packages?
[...]
i think this sounds great. probably crm.el should go in edit-utils.
does this need to be ported or does it work already under xemacs?
Thank you for your response. I've done some testing with XEmacs
21.4.15:
`crm.el' from Emacs 21 (21.3 or 21.4) works without any modifications
in XEmacs. The version from Emacs 22 (CVS) uses the function
`minibuffer-prompt-end' (a `diff -w -u' of those versions is
attached), a built-in function in Emacs 22, not present in XEmacs.
AfAICS, it would be sufficient if you'd include the Emacs 21 version
of `crm.el' in edit-utils. [My understanding is, that XEmacs users
(regardless whether they use a recent XEmacs 21.4 or XEmacs 21.5)
would then just need to upgrade the edit-utils package to get this.
Please CMIIW.]
It would be great if you could include `crm.el' in the next packages
updates. TIA.
In case you consider to use the Emacs 22 version, here's some
additional information. I don't know if XEmacs has similar functions
that could be used:
,----[ <f1> f minibuffer-prompt-end RET ]
| minibuffer-prompt-end is a built-in function in `C source code'.
| (minibuffer-prompt-end)
|
| Return the buffer position of the end of the minibuffer prompt.
| Return (point-min) if current buffer is not a minibuffer.
`----
In Emacs 21, `minibuffer-prompt-end' is defined in `simple.el':
,----
| (defun minibuffer-prompt-end ()
| "Return the buffer position of the end of the minibuffer prompt.
| Return (point-min) if current buffer is not a mini-buffer."
| (field-beginning (point-max)))
`----
,----[ <f1> f field-beginning RET ]
| field-beginning is a built-in function.
| (field-beginning &optional POS ESCAPE-FROM-EDGE)
|
| Return the beginning of the field surrounding POS.
| A field is a region of text with the same `field' property.
| If POS is nil, the value of point is used for POS.
| If ESCAPE-FROM-EDGE is non-nil and POS is at the beginning of its
| field, then the beginning of the *previous* field is returned.
`----
HTH.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
6:16 a.m.
New subject: Review lags [was: crm.el ...]
>>>> "Reiner" == Reiner Steib
<reinersteib+gmane(a)imap.cc> writes:
Reiner> Can we expect _any_ reaction (yes, no, maybe) from the
Reiner> XEmacs board?
Unfortunately, at this time we're very short-handed for reviewers and
developers in general. If there was negative feeling, you'd get a
"no", so the answer is "maybe" until it turns into "yes".
This is a
shortcoming of our relatively decentralized process.
Reiner> Am I posting to the wrong list?
No and yes. For what you posted that I'm responding to, this is the
right place.
If you want to help something to get done a lot faster, you can post a
full patch (in the case of a new file, either a patch against
/dev/null or the file as an attachment is OK), with appropriate
XEmacs-format changelog, to XEmacs Patches
<xemacs-patches(a)xemacs.org>.
An analysis of any extra work needed to make the package compatible
with both XEmacs 21.4 (preferably tested with the most recent release,
but that's not absolutely necessary) and XEmacs 21.5 (tested with CVS
head by preference, or at least the most recent beta release) is very
helpful. (For example, the information you posted in response to Ben
in <v9wtk4a86h.fsf(a)marauder.physik.uni-ulm.de> later in this thread is
excellent.)
Yes, I'm aware of how much work that is. Somebody has to do it,
though, and it won't get in until that's done to the satisfaction of
at least one review board member. If you wait for us to do it, it
will take longer. Whether it's worth it is something for you to decide.
Regards,
Steve
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
12:40 p.m.
New subject: Review lags [was: crm.el ...]
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
>>>> "Reiner" == Reiner Steib <reinersteib+gmane(a)imap.cc>
writes:
Reiner> Can we expect _any_ reaction (yes, no, maybe) from the XEmacs
Reiner> board?
Stephen> Unfortunately, at this time we're very short-handed for
Stephen> reviewers and developers in general. If there was negative
Stephen> feeling, you'd get a "no", so the answer is "maybe"
until it
Stephen> turns into "yes". This is a shortcoming of our relatively
Stephen> decentralized process.
Reiner> Am I posting to the wrong list?
Stephen> No and yes. For what you posted that I'm responding to, this
Stephen> is the right place.
Stephen> If you want to help something to get done a lot faster, you
Stephen> can post a full patch (in the case of a new file, either a
Stephen> patch against /dev/null or the file as an attachment is OK),
Stephen> with appropriate XEmacs-format changelog, to XEmacs Patches
Stephen> <xemacs-patches(a)xemacs.org>.
[...]
I did just that about a year ago -- I posted a reasonably simple patch
that adds about 4 lines of code to the XEmacs code base. I brought the
issue up again about three weeks ago, and a couple of days ago, but it
seems continuous nagging doesn't get me anywhere.
The patch (mswindows window id property for XEmacs frames) is necessary,
because without it I cannot support people who want to use my vx-mode
package for dictation with XEmacs under Windows. As it is, my user base
is limited to people who use Linux and run Dragon NaturallySpeaking
under VMware, a rather rare combination.
I'm getting increasingly disappointed -- I initially switched to XEmacs
because I found the developer community to be more responsive and code
would change quicker. I hate sending those nagging E-mails, it annoys
the developers, it annoys me, and causes people to dislike me for no
good reason. Should I just give up, rework vx-mode to use properties
instead of extents and switch to FSF Emacs?
I understand "being short-handed for developers", but this attitude will
cause even more developers to go elsewhere.
--J.
1:02 p.m.
New subject: Review lags
Jan Rychter <jan(a)rychter.com> writes:
>>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Stephen> If you want to help something to get done a lot faster,
Stephen> you can post a full patch (in the case of a new file,
Stephen> either a patch against /dev/null or the file as an
Stephen> attachment is OK), with appropriate XEmacs-format
Stephen> changelog, to XEmacs Patches <xemacs-patches(a)xemacs.org>.
[...]
I did just that about a year ago -- I posted a reasonably simple
patch that adds about 4 lines of code to the XEmacs code base. I
brought the issue up again about three weeks ago, and a couple of
days ago, but it seems continuous nagging doesn't get me anywhere.
The patch (mswindows window id property for XEmacs frames) is
necessary, because without it I cannot support people who want to
use my vx-mode package for dictation with XEmacs under Windows. As
it is, my user base is limited to people who use Linux and run
Dragon NaturallySpeaking under VMware, a rather rare combination.
I'm getting increasingly disappointed -- I initially switched to
XEmacs because I found the developer community to be more responsive
and code would change quicker. I hate sending those nagging E-mails,
it annoys the developers, it annoys me, and causes people to dislike
me for no good reason. Should I just give up, rework vx-mode to use
properties instead of extents and switch to FSF Emacs?
I understand "being short-handed for developers", but this attitude
will cause even more developers to go elsewhere.
The keyword here is "developer". If you are a developer, try getting
CVS access. The person checking the code in has to take the moral
responsibility for fixing it in case something breaks. So things just
work out faster if you do it yourself instead of trying to make
somebody else do it.
Once you get the code into XEmacs, it will usually be released within
a few months. Once you get some code into Emacs, it will usually be
released within a few years. Except that quite a number of serious
users don't wait for releases and use developer snapshots.
Getting some code into Emacs for the purpose of providing a
Windows-only feature will not sit well with Richard Stallman. You
might as well forget it. So you will first have to think of a general
pattern of use that would make it good for applications under Unixy
operating systems too, get yourself or somebody else to implement it
there, and then add the Windows functionality with the same interface.
Personally, I found working on Emacs and with Emacs developers
decidedly less aggravating than what I experienced with XEmacs. But
tastes differ, and your particular demands do not exactly sound like
you'd likely be overenthused with the Emacs development model, either.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
5:01 a.m.
New subject: Review lags [was: crm.el ...]
Jan Rychter wrote:
>>>>>"Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
>>>>>"Reiner" == Reiner Steib <reinersteib+gmane(a)imap.cc>
writes:
>>>>>
>>>>>
Reiner> Can we expect _any_ reaction (yes, no, maybe) from the XEmacs
Reiner> board?
Stephen> Unfortunately, at this time we're very short-handed for
Stephen> reviewers and developers in general. If there was negative
Stephen> feeling, you'd get a "no", so the answer is "maybe"
until it
Stephen> turns into "yes". This is a shortcoming of our relatively
Stephen> decentralized process.
Reiner> Am I posting to the wrong list?
Stephen> No and yes. For what you posted that I'm responding to, this
Stephen> is the right place.
Stephen> If you want to help something to get done a lot faster, you
Stephen> can post a full patch (in the case of a new file, either a
Stephen> patch against /dev/null or the file as an attachment is OK),
Stephen> with appropriate XEmacs-format changelog, to XEmacs Patches
Stephen> <xemacs-patches(a)xemacs.org>.
[...]
I did just that about a year ago -- I posted a reasonably simple patch
that adds about 4 lines of code to the XEmacs code base. I brought the
issue up again about three weeks ago, and a couple of days ago, but it
seems continuous nagging doesn't get me anywhere.
The patch (mswindows window id property for XEmacs frames) is necessary,
because without it I cannot support people who want to use my vx-mode
package for dictation with XEmacs under Windows. As it is, my user base
is limited to people who use Linux and run Dragon NaturallySpeaking
under VMware, a rather rare combination.
I'm getting increasingly disappointed -- I initially switched to XEmacs
because I found the developer community to be more responsive and code
would change quicker. I hate sending those nagging E-mails, it annoys
the developers, it annoys me, and causes people to dislike me for no
good reason. Should I just give up, rework vx-mode to use properties
instead of extents and switch to FSF Emacs?
I understand "being short-handed for developers", but this attitude will
cause even more developers to go elsewhere.
hello Jan. i checked your feature to the latest CVS. i have to
personally apologize for not getting to this sooner; too much has been
going on lately. i changed it slightly so that the value of the
`window-id' property is a string, like in X windows. also, it is
currently only available through `frame-property'; i didn't implement
`mswindows-window-id'. (if we want something like this, it should be
called `frame-window-id'.)
please also note that david kastrup's views are not shared by the xemacs
developers as a whole. i for one am committed to having good ms windows
support in xemacs, and in fact do all my development under windows [with
lots of help from cygwin].
ben
7:33 a.m.
New subject: Review lags
Ben Wing <ben(a)xemacs.org> writes:
Jan Rychter wrote:
>>>>>>"Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
>>>>>>"Reiner" == Reiner Steib
<reinersteib+gmane(a)imap.cc> writes:
>>>>>>
>>>>>>
> Reiner> Can we expect _any_ reaction (yes, no, maybe) from the XEmacs
> Reiner> board?
>
> Stephen> Unfortunately, at this time we're very short-handed for
> Stephen> reviewers and developers in general. If there was negative
> Stephen> feeling, you'd get a "no", so the answer is
"maybe" until it
> Stephen> turns into "yes". This is a shortcoming of our relatively
> Stephen> decentralized process.
>
> Reiner> Am I posting to the wrong list?
>
> Stephen> No and yes. For what you posted that I'm responding to, this
> Stephen> is the right place.
>
> Stephen> If you want to help something to get done a lot faster, you
> Stephen> can post a full patch (in the case of a new file, either a
> Stephen> patch against /dev/null or the file as an attachment is OK),
> Stephen> with appropriate XEmacs-format changelog, to XEmacs Patches
> Stephen> <xemacs-patches(a)xemacs.org>.
>[...]
>
>I did just that about a year ago -- I posted a reasonably simple patch
>that adds about 4 lines of code to the XEmacs code base. I brought the
>issue up again about three weeks ago, and a couple of days ago, but it
>seems continuous nagging doesn't get me anywhere.
>
>The patch (mswindows window id property for XEmacs frames) is necessary,
>because without it I cannot support people who want to use my vx-mode
>package for dictation with XEmacs under Windows. As it is, my user base
>is limited to people who use Linux and run Dragon NaturallySpeaking
>under VMware, a rather rare combination.
>
>I'm getting increasingly disappointed -- I initially switched to XEmacs
>because I found the developer community to be more responsive and code
>would change quicker. I hate sending those nagging E-mails, it annoys
>the developers, it annoys me, and causes people to dislike me for no
>good reason. Should I just give up, rework vx-mode to use properties
>instead of extents and switch to FSF Emacs?
>
>I understand "being short-handed for developers", but this attitude will
>cause even more developers to go elsewhere.
>
>
hello Jan. i checked your feature to the latest CVS. i have to
personally apologize for not getting to this sooner; too much has been
going on lately. i changed it slightly so that the value of the
`window-id' property is a string, like in X windows. also, it is
currently only available through `frame-property'; i didn't implement
`mswindows-window-id'. (if we want something like this, it should be
called `frame-window-id'.)
please also note that david kastrup's views are not shared by the
xemacs developers as a whole. i for one am committed to having good
ms windows support in xemacs, and in fact do all my development under
windows [with lots of help from cygwin].
Hello Ben, I think you misunderstood David, who was talking about
Emacs' (specifically RMS') commitment to Windows support, not XEmacs'.
ben
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
10:27 a.m.
New subject: Review lags
Ben Wing <ben(a)xemacs.org> writes:
please also note that david kastrup's views are not shared by
the
xemacs developers as a whole.
Care to point out a single sentence of mine where you disagree?
i for one am committed to having good ms windows support in xemacs,
and in fact do all my development under windows [with lots of help
from cygwin].
Since when have you changed your name to "Richard Stallman" and the
name of your project to "Emacs"?
I have not been talking about XEmacs at all. If you had bothered
actually reading what I have written, this should not have escaped
you. I was addressing the OP's contention that his purposes might be
better served with Emacs than XEmacs.
Given that you suffer from RSI, you could save your wrists some pain
by just reading through what you think you are replying to. I find
this simply unbelievable.
So that you don't have to look for it, I'll save yourself the work by
giving the message Id:
Message-ID: <85ek6b86nn.fsf(a)lola.goethe.zz>
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
1:18 p.m.
New subject: Review lags [was: crm.el ...]
>>>> "Ben" == Ben Wing <ben(a)xemacs.org>
writes:
Ben> hello Jan. i checked your feature to the latest CVS. i have to
Ben> personally apologize for not getting to this sooner; too much has
Ben> been going on lately. i changed it slightly so that the value of
Ben> the `window-id' property is a string, like in X windows. also, it
Ben> is currently only available through `frame-property'; i didn't
Ben> implement `mswindows-window-id'. (if we want something like this,
Ben> it should be called `frame-window-id'.)
Ben,
Thanks for the checkin. Hopefully it'll be smoother next time. The
changes are perfectly fine, I don't actually much care about the way
this value is accessed, I just want it to be accessible.
best regards,
--Jan
8:17 a.m.
New subject: Review lags [was: crm.el ...]
>>>> "Jan" == Jan Rychter
<jan(a)rychter.com> writes:
Jan> I did just that about a year ago -- I posted a reasonably
Jan> simple patch that adds about 4 lines of code to the XEmacs
Jan> code base. I brought the issue up again about three weeks
Jan> ago, and a couple of days ago, but it seems continuous
Jan> nagging doesn't get me anywhere.
I'm sorry about that. Your patch is not one I'm competent to review.
As far as I knew, Ben was aware of it (and in fact has since committed
it), so I left it at that.
Jan> I understand "being short-handed for developers", but this
Jan> attitude will cause even more developers to go elsewhere.
It's not an "attitude", it's a fact. If saying so would make
developers go elsewhere, I think it's only fair to say so so they can
make an informed choice: go, or ask for the authority to make it
happen themselves.
If you want to accept the responsibility (ie, to review _some_ of
other people's small patches) and get the authority (to commit them),
write to xemacs-review(a)xemacs.org and say you want to be a reviewer.
I can't say it's a done deal, but I know your posts and patches well
enough to support you; I suppose there are probably other reviewers
who would, too.
By the way, as far as I'm concerned, people who have been contributing
for a while, even just bug reports, are welcome to nominate themselves
to the review board. It does require that the current reviewers be
able to assess your ability to review, so you need a public track
record as a developer somewhere (preferably in XEmacs, of course) or a
strong sponsor already on the board.
You're welcome to ask for more information, from me, at least. If you
know other reviewers well enough, you could ask them too (there's a
list at http://www.xemacs.org/develop/jobs.html). My guess is most
would welcome inquiries, but I'm the only one I _know_ does. :-)
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
1:21 p.m.
New subject: Review lags [was: crm.el ...]
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
>>>> "Jan" == Jan Rychter <jan(a)rychter.com> writes:
Jan> I did just that about a year ago -- I posted a reasonably simple
Jan> patch that adds about 4 lines of code to the XEmacs code base. I
Jan> brought the issue up again about three weeks ago, and a couple of
Jan> days ago, but it seems continuous nagging doesn't get me anywhere.
Stephen> I'm sorry about that. Your patch is not one I'm competent to
Stephen> review. As far as I knew, Ben was aware of it (and in fact
Stephen> has since committed it), so I left it at that.
Jan> I understand "being short-handed for developers", but this
Jan> attitude will cause even more developers to go elsewhere.
Stephen> It's not an "attitude", it's a fact. If saying so would
make
Stephen> developers go elsewhere, I think it's only fair to say so so
Stephen> they can make an informed choice: go, or ask for the authority
Stephen> to make it happen themselves.
Stephen> If you want to accept the responsibility (ie, to review _some_
Stephen> of other people's small patches) and get the authority (to
Stephen> commit them), write to xemacs-review(a)xemacs.org and say you
Stephen> want to be a reviewer. I can't say it's a done deal, but I
Stephen> know your posts and patches well enough to support you; I
Stephen> suppose there are probably other reviewers who would, too.
Stephen> By the way, as far as I'm concerned, people who have been
Stephen> contributing for a while, even just bug reports, are welcome
Stephen> to nominate themselves to the review board. It does require
Stephen> that the current reviewers be able to assess your ability to
Stephen> review, so you need a public track record as a developer
Stephen> somewhere (preferably in XEmacs, of course) or a strong
Stephen> sponsor already on the board.
Well, I don't feel competent enough to review code or to deeply
participate in development. I make small changes and fixes which really
need reviewing by more knowledgeable people. Hence, I believe my role
isn't to review, but to submit patches and report bugs.
--J.
6964
days inactive
6978
days old
13 comments
7 participants
participants (7)
-
Adrian Aichner -
Ben Wing -
David Kastrup -
Jan Rychter -
Reiner Steib -
Stephen J. Turnbull -
Uwe Brauer