Chuck,
We've been bombarded as of late with the bug in checkX (run2) 0.3.0 not
respecting the -t option. 0.3.1-1 seems to fix that; could this be made
curr: ASAP?
Yaakov
Cygwin/X
Yaakov (Cygwin/X) wrote:
We've been bombarded as of late with the bug in checkX (run2) 0.3.0 not
respecting the -t option. 0.3.1-1 seems to fix that; could this be made
curr: ASAP?
run2-0.3.2-1 should hit the mirrors any time now (no code changes from
0.3.1-1 except to bump to an even micro
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Just to be clear from the start, Cygwin 1.7 not 1.5.
ACK.
*blush* Sorry!
...
Thus, once more: What does
md5sum /usr/bin/checkX
yield?
a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216?
The 2nd:
On 12/01/2009 12:29 PM, Mike Ayers wrote:
Apologies for sending this to the list, but I could not find the answer
on the web pages. I'm having a few quirks with the mailing list that I'd like
to ask the postmaster about, but I can't find a contact point. Does anyone
know of one?
Hi All:
This is my first post here. I've never had a problem I couldn't fix
with cygwin-x before.
Here is the deal:
I just bought a new PC with windows 7 64 bit, build number 7600,
version 6.1.
I downloaded a fresh install of cygwin and cannot get cygwin-x xterm
running. Cygwin
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
[...]
Thus, once more: What does
md5sum /usr/bin/checkX
yield?
a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216?
The 2nd:
vhaisbtim...@isb-timaresbrian-lt ~
$ md5sum /usr/bin/checkX
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
$ checkX -v
run2 0.3.0
So, you've got the situation I surmised in
http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html
Grr, I saw that, went and _thought_ I got the right version but
it seems the right version
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
$ checkX -v
run2 0.3.0
So, you've got the situation I surmised in
http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html
Grr, I saw that, went and _thought_ I got the right version
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
The X window showed up, but it blew up real good (the windows
disappeared, then the X icon. After a rebootit
didn't launch at all. I ran startxwin.sh from the Cygwin Bash
Shell, and it started.
At least we're getting *somewhere* :-)
CVSROOT:/cvs/src
Module name:src
Changes by: cori...@sourceware.org 2009-12-01 16:31:04
Modified files:
winsup/cygwin : ChangeLog fhandler_registry.cc
Log message:
* fhandler_registry.cc (fhandler_registry::open): Mark /proc/registry
directory and
On Nov 30 20:53, Robert Pendell wrote:
On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi
angelo.grazi...@alice.it wrote:
Robert Pendell wrote:
P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set and
patch defaulted to /tmp.
I noticed that too...
Ken Brown wrote:
On Nov 30 17:04, Ken Brown wrote:
The discussion currently going on in the thread
http://cygwin.com/ml/cygwin/2009-11/threads.html#00892
makes me think that the section on environment variables in the
user's guide (http://cygwin.com/1.7/cygwin-ug-net/setup-env.html)
could use some
On Nov 30 11:23, Corinna Vinschen wrote:
On Nov 26 22:42, Jeremy Hetzler wrote:
I have cvs on a client machine connecting to a host over ssh. The cvs
procedure finishes, but the connection does not terminate until I hit
ctrl-c. The cvs process is then left running on the host. Regular ssh
On Tue, December 1, 2009 9:15 am, Corinna Vinschen wrote:
On Nov 30 20:53, Robert Pendell wrote:
On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi
angelo.grazi...@alice.it wrote:
Robert Pendell wrote:
P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were not set
and
patch defaulted
Hi All,
I'm not sure if this is expected behaviour or not, but I've noticed
the following:
csutc...@eush65 /proc
$ find .
.
./loadavg
./meminfo
./registry
find: `./registry': Bad file descriptor
./stat
./version
./uptime
./cpuinfo
./partitions
./self
./mounts
./registry32
find:
After I viewed setup.ini, I decide to write a little script to do this.
Currently, it scans all the sub-directory of cygwin local package directory,
and delete all the old files which not listed in setup.ini or setup-2.ini.
Wish it can help someone like me.
download it from nabble.com:
On 12/1/2009 5:44 AM, John Morrison wrote:
On Tue, December 1, 2009 9:15 am, Corinna Vinschen wrote:
I'm wondering if /etc/profile is actually the right place for unsetting
TMP and TEMP. What about etc/defaults/etc/skel/.bashrc instead? It
allows every user simple access to the setting of TMP
Ken Brown wrote:
Here's one possibility, but it may be a little too verbose:
Melius abundare quam deficere!
I want just to flag that in the next release of base-files package, one
should remove '/usr/X11R6/bin' from the definition of PATH. But,
perhaps, this is already in John's ToDo list.
2009/12/1 Ken Brown:
On 12/1/2009 5:44 AM, John Morrison wrote:
Unsetting them in the skel .bashrc files shouldn't be a problem to do, but
on my system...
$ echo $TMP
/cygdrive/c/DOCUME~1/morrijr/LOCALS~1/Temp
Tue Dec 01 10:40 AM
$ unset TMP
Tue Dec 01 10:40 AM
$ echo $TMP
Tue Dec
On Tue, Dec 01, 2009 at 04:31:48AM -0800, LiuYan ?? wrote:
After I viewed setup.ini, I decide to write a little script to do this.
Currently, it scans all the sub-directory of cygwin local package
directory, and delete all the old files which not listed in setup.ini
or setup-2.ini.
You didn't
Hi Christopher, I've figure out one reason in my first post: Our servers have
NO internet connection, so I'd better to keep a local copy of install
packages, so that I can upgrade cygwin on servers by choose Install from
Local Directory setup type.
There's another reason I don't want to talk
On Mon, Nov 30, 2009 at 07:40:51PM -0600, Jeremy Bopp wrote:
[...]
If you want to see the Windows PATH setting unmolested by Cygwin, you
will either need to strip out the additions set by /etc/profile or avoid
running under an environment modified by /etc/profile.
It doesn't add, actually -
2009/12/1 Reinier Post:
If you want to see the Windows PATH setting unmolested by Cygwin, you
will either need to strip out the additions set by /etc/profile or avoid
running under an environment modified by /etc/profile.
It doesn't add, actually - it replaces it.
You're wrong. The Cygwin
On Tue, Dec 01, 2009 at 07:15:43AM -0800, LiuYan ?? wrote:
Hi Christopher, I've figure out one reason in my first post: Our
servers have NO internet connection, so I'd better to keep a local copy
of install packages, so that I can upgrade cygwin on servers by choose
Install from Local
On Dec 1 06:31, Chris Sutcliffe wrote:
Hi All,
I'm not sure if this is expected behaviour or not, but I've noticed
the following:
csutc...@eush65 /proc
$ find .
.
./loadavg
./meminfo
./registry
find: `./registry': Bad file descriptor
This is a bug in Cygwin. It misses to set a
On Dec 1 08:12, Ken Brown wrote:
On 12/1/2009 5:44 AM, John Morrison wrote:
They don't get 'reset' to the windows default... but then, I've not really
been following this thread. Is that what's wanted?
No, they're not expected to get reset.
Also, $PATCH and $TMPDIR weren't defined on my
On Dec 1 14:24, Angelo Graziosi wrote:
Ken Brown wrote:
Here's one possibility, but it may be a little too verbose:
Melius abundare quam deficere!
I want just to flag that in the next release of base-files package,
one should remove '/usr/X11R6/bin' from the definition of PATH. But,
On Tue, Dec 1, 2009 at 5:44 AM, John Morrison wrote:
On Tue, December 1, 2009 9:15 am, Corinna Vinschen wrote:
On Nov 30 20:53, Robert Pendell wrote:
On Mon, Nov 30, 2009 at 6:37 PM, Angelo Graziosi
wrote:
Robert Pendell wrote:
P.S. - On linux (when I tested) TEMP, TMP, and TMPDIR were
On 12/1/2009 4:45 AM, Corinna Vinschen wrote:
On Nov 30 17:04, Ken Brown wrote:
The discussion currently going on in the thread
http://cygwin.com/ml/cygwin/2009-11/threads.html#00892
makes me think that the section on environment variables in the
user's guide
Hi,
After testing this with a latest version of perl (5.10.1-1) / cygwin (1.7),
we still see:
[r...@quad32]~: perl --version
This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int
(with 12 registered patches, see perl -V for more detail)
Copyright 1987-2009, Larry Wall
Perl may be
Just to be 100% clear its not the fact that the script errors, its the fact
that the permissions after the initial DOS pathed chmod doesn't actually set
the permissions correctly and doesn't throw any error.
Regards
Steve
- Original Message -
From: Dan Offord
Steven Hartland wrote:
Just to be 100% clear its not the fact that the script errors, its the fact
that the permissions after the initial DOS pathed chmod doesn't actually
set the permissions correctly and doesn't throw any error.
Also, it's not just perl, you can reproduce it in a shell:
On Dec 1 17:42, Dave Korn wrote:
Steven Hartland wrote:
Just to be 100% clear its not the fact that the script errors, its the fact
that the permissions after the initial DOS pathed chmod doesn't actually
set the permissions correctly and doesn't throw any error.
Also, it's not just
On Dec 1 11:32, Ken Brown wrote:
On 12/1/2009 4:45 AM, Corinna Vinschen wrote:
On Nov 30 17:04, Ken Brown wrote:
I would be willing to take a stab at writing a patch if the
developers think this would be useful.
That sounds like a nice idea.
OK, my patch is attached. It anticipates the
update:
added -p option, which will treat files listed in [prev] section of
setup.ini as old.
now, run
./cleanOldPackages_UTF8.sh -p -d
will clean files listed in [prev] sectoin.
download it from nabble.com:
http://old.nabble.com/file/p26594254/cleanOldPackages_UTF8.sh
cleanOldPackages_UTF8.sh
Corinna Vinschen wrote:
That's by design. When you use Win32 paths, instead of POSIX paths,
you will get Win32 default permission handling. Or, in other words,
for all DOS paths the mount mode is noacl.
Cheers, I was just off looking that up. It's obviously what's happening for
perl
- Original Message -
From: Corinna Vinschen
That's by design. When you use Win32 paths, instead of POSIX paths,
you will get Win32 default permission handling. Or, in other words,
for all DOS paths the mount mode is noacl.
Ok that begs the questions:-
1. What was the reasoning
On Tue, Dec 01, 2009 at 11:32:43AM -0500, Robert Pendell wrote:
They are not reset but during an strace I discovered that cygwin will
internally default to the system defined TEMP if one isn't defined in
cygwin. In other words if it has been unset. This is similar to
linux using /tmp by default
On Dec 1 18:03, Steven Hartland wrote:
- Original Message - From: Corinna Vinschen
That's by design. When you use Win32 paths, instead of POSIX paths,
you will get Win32 default permission handling. Or, in other words,
for all DOS paths the mount mode is noacl.
Ok that begs the
On Tue, Dec 1, 2009 at 10:03 AM, Andy Koppe wrote:
2009/12/1 Reinier Post:
If you want to see the Windows PATH setting unmolested by Cygwin, you
will either need to strip out the additions set by /etc/profile or avoid
running under an environment modified by /etc/profile.
It doesn't add,
On Tue, Dec 1, 2009 at 1:03 PM, Christopher Faylor wrote:
On Tue, Dec 01, 2009 at 11:32:43AM -0500, Robert Pendell wrote:
They are not reset but during an strace I discovered that cygwin will
internally default to the system defined TEMP if one isn't defined in
cygwin. In other words if it has
On Tue, December 1, 2009 4:32 pm, Ken Brown wrote:
On 12/1/2009 4:45 AM, Corinna Vinschen wrote:
On Nov 30 17:04, Ken Brown wrote:
The discussion currently going on in the thread
http://cygwin.com/ml/cygwin/2009-11/threads.html#00892
makes me think that the section on environment
Ok, I've removed the X11R6 from the path and unset TMP and TEMP in the
skel/.bashrc. Are there any other changes folks would like before I roll
this up?
:)
Regards,
J.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
- Original Message -
From: Corinna Vinschen
Win32 path - No POSIX path - no POSIX permissions.
So then why does it have any permissions support at all? By allowing
permissions to be read and obeyed, but not written, your sending out
very much mixed messaging which is confusing at
DePriest, Jason R. wrote:
On Tue, Dec 1, 2009 at 10:03 AM, Andy Koppe wrote:
2009/12/1 Reinier Post:
If you want to see the Windows PATH setting unmolested by Cygwin, you
will either need to strip out the additions set by /etc/profile or avoid
running under an environment modified by
On 01/12/2009 19:37, John Morrison wrote:
Ok, I've removed the X11R6 from the path and unset TMP and TEMP in the
skel/.bashrc. Are there any other changes folks would like before I roll
this up?
It would be nice to audit all the existing packages to see if there are any
which still install
To verify it, all you have to do is open a bash prompt (Cygwin.bat,
mintty, rxvt, whatever) and then launch a cmd.exe or powershell.
Check the path in the bash prompt and you will see the cygwin stuff at
the beginning of it.
Check the path in the cmd.exe or powershell prompt which was run
My subject keeps getting blocked due to spam-like keywords, perhaps
it will work this time:
I'd like to report this here but I don't really have a general
solution. Perhaps someone who knows better can comment.
In git-1.6.1.2 [1.5] and git-1.6.4.2 [1.7] there is a command called
'git-mergetool'
On Tue, Dec 1, 2009 at 2:24 PM, Lee Maschmeyer wrote:
To verify it, all you have to do is open a bash prompt (Cygw
0/tty2W0(2)$ echo $PATH
/home/lmaschm/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/c/Program
Files/Common Files/Microsoft Shared/Windows Live:/c/WINDOWS
Lee Maschmeyer wrote:
To verify it, all you have to do is open a bash prompt (Cygwin.bat,
mintty, rxvt, whatever) and then launch a cmd.exe or powershell.
Check the path in the bash prompt and you will see the cygwin stuff at
the beginning of it.
Check the path in the cmd.exe or powershell
On Dec 1 19:37, Steven Hartland wrote:
- Original Message - From: Corinna Vinschen
Win32 path - No POSIX path - no POSIX permissions.
So then why does it have any permissions support at all? By allowing
permissions to be read and obeyed, but not written, your sending out
very
On Dec 1 19:24, John Morrison wrote:
On Tue, December 1, 2009 4:32 pm, Ken Brown wrote:
OK, my patch is attached. It anticipates the change to the default
.bashrc file that we've been discussing in the thread cited above.
Hi Ken,
While I think it's a good idea to point out that they
David Antliff wrote:
In git-1.6.1.2 [1.5] and git-1.6.4.2 [1.7] there is a command called
'git-mergetool' that is used as a wrapper for various graphical
merging tools, such as kdiff3. It makes local copies of the relevant
commits and brings up an interactive gui for resolving merge conflicts.
On 01/12/2009 20:17, Jon TURNEY wrote:
On 01/12/2009 19:37, John Morrison wrote:
Ok, I've removed the X11R6 from the path and unset TMP and TEMP in the
skel/.bashrc. Are there any other changes folks would like before I roll
this up?
It would be nice to audit all the existing packages to see
Hello,
While making effort to port minitage [1] to windows, i had in mind to test
cygwin2 (setup-1.7.exe as i understood) as it as improved support for some
things like getaddrinfo and posix threads.
Indeed the goal is to recompile a bunch of libraries from sources, then make
them link together,
ran cmd.exe from start menu
And that gets the info into Cygwin - how?
--
Lee Maschmeyer
Wayne State University
Detroit, Michigan, USA
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Lee Maschmeyer wrote:
ran cmd.exe from start menu
And that gets the info into Cygwin - how?
Yet another false inference. You were being shown an illustrative
comparison that was supposed to demonstrate a point about the underlying
mechanisms in play, not an answer to the original
On Wed, Dec 2, 2009 at 10:11, Jeremy Bopp wrote:
David Antliff wrote:
On the other hand, this command does work:
kdiff3 --auto --L1 build.xml (A) --L2 build.xml (B)
c:/cygwin-1.7/tmp/Vc0BZy_build.xml build.xml
As a fairly simple workaround, you could create a wrapper script which
takes the
2009/12/1 David Antliff:
I need a way to
translate /tmp to the Cygwin installation directory. I.e. it's not a
simple case of replacing /tmp with c:/tmp but rather
$CYGWIN_INSTALL_DIR/tmp and I'm not sure CYGWIN_INSTALL_DIR or
anything similar exists.
Have a look at the cygpath utility.
Andy
David Antliff wrote:
On Wed, Dec 2, 2009 at 10:11, Jeremy Bopp wrote:
David Antliff wrote:
On the other hand, this command does work:
kdiff3 --auto --L1 build.xml (A) --L2 build.xml (B)
c:/cygwin-1.7/tmp/Vc0BZy_build.xml build.xml
As a fairly simple workaround, you could create a wrapper
On 12/1/2009 4:08 PM, Corinna Vinschen wrote:
On Dec 1 19:24, John Morrison wrote:
On Tue, December 1, 2009 4:32 pm, Ken Brown wrote:
OK, my patch is attached. It anticipates the change to the default
.bashrc file that we've been discussing in the thread cited above.
Hi Ken,
While I think
On 12/01/2009 04:27 PM, kiorky wrote:
Hello,
While making effort to port minitage [1] to windows, i had in mind to test
cygwin2 (setup-1.7.exe as i understood) as it as improved support for some
things like getaddrinfo and posix threads.
Indeed the goal is to recompile a bunch of libraries from
On Wed, Dec 2, 2009 at 10:58, Jeremy Bopp jer...@bopp.net wrote:
There is a purpose built tool specifically to handle this which I
mentioned in my reply.
My apologies - I am familiar with the cygpath tool but I had never
realised that it treats paths in the cygwin directory like that. I had
On Tue, Dec 01, 2009 at 12:42:01PM -0600, DePriest, Jason R. wrote:
On Tue, Dec 1, 2009 at 10:03 AM, Andy Koppe wrote:
2009/12/1 Reinier Post:
If you want to see the Windows PATH setting unmolested by Cygwin, you
will either need to strip out the additions set by /etc/profile or avoid
Windows programs will only ever see a Windows-style PATH no matter what;
however, they WILL see the Cygwin paths converted to Windows-style and
prepended IF they were run from a login shell under Cygwin.
Yes, that's how I'm getting these Message too long messages.
--
Reinier
--
Problem
On 12/01/2009 05:31 PM, kiorky wrote:
Larry Hall (Cygwin) a écrit :
Can we see *attached* cygcheck output for your 1.7 and 1.5 installs, as
1.out - cygwin
2.out - cygwin2
Thanks. Since cygcheck for 1.5 doesn't find gcc and you have tools from
other sources installed, I have to ask, are
Cygwin,
I just got my free customizable page on Blastoff that combines the best news,
videos, music, and social networking with cash-back shopping from the biggest
retailers such as Microsoft, Radioshack, Expedia, and Office Max. You should
check it out; it's great.
Hi Cygwin Codyburrows.
You should check it out; it's great. I just got my free Blastoff site. It's a
customizable page that combines the best news, videos, music, and social
networking with cash-back shopping from the biggest retailers such as Orbitz,
Expedia, Old Navy, and Hotels .com.
On Tue, Dec 01, 2009 at 06:28:47PM -0500, Larry Hall (Cygwin) wrote:
On 12/01/2009 05:31 PM, kiorky wrote:
Larry Hall (Cygwin) a ??crit :
Can we see *attached* cygcheck output for your 1.7 and 1.5 installs, as
1.out - cygwin
2.out - cygwin2
Thanks. Since cygcheck for 1.5 doesn't find gcc
On Wed, Dec 02, 2009 at 12:28:31AM +0100, Reinier Post wrote:
Windows programs will only ever see a Windows-style PATH no matter
what; however, they WILL see the Cygwin paths converted to
Windows-style and prepended IF they were run from a login shell under
Cygwin.
Yes, that's how I'm getting
On 12/01/2009 04:34 PM, SEANPAUL JONES wrote:
Hi Cygwin Codyburrows.
Here's a clue...
--
Andrew DeFaria http://defaria.com
If god wanted people to believe in him, then why did he invent logic?.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
My program ran fine under cygwin 1.5 as well as many versions of
linux including
mandriva 2009, mandriva 2009.1 and mandriva 2010.0
When compiled with
gcc cal.c -o cal
and run with
cal 2009
I get a segmentation fault.
When I uncomment line 62, the program runs successfully.
I have had other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 12/1/2009 9:13 AM:
This one appears to be a bug in find. It looks like it's using its own
version of the fts(3) functions. AFAICS, what happens is that find uses
fstatat(fd = /proc/$PID/fd, name=6) in the first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ken Brown on 12/1/2009 2:59 PM:
I agree. A revised patch is attached.
+You may therefore want to unset them by adding the following two lines
+to your filename.bashrc/filename file:
filename~/.bashrc/filename
- --
Don't work too
The run2 package provides two utilities: 'run2' and 'checkX' (as
the package is actually a renamed and updated successor to the
now-obsoleted checkx package). The first utility is a more powerful
replacement for the venerable 'run' utility that has long been a
part of the cygwin distribution. The
Linda Walsh previously wrote:
Dunno about the rest, but I rsync from a mounted MS-Windows
^^^
CIFS share every night to a linux server. It's never hung. So I
don't know
about the
The run package provides a simple application to launch console programs
with their console hidden.
[[ compiled using gcc-3.4.4-999 ]]
CHANGES since run-1.1.12-1
* Ensure stdout and stderr in inferior are distinct.
--
Charles Wilson
volunteer run maintainer for
The run package provides a simple application to launch console programs
with their console hidden.
[[ compiled using gcc-4.3.4-1 ]]
CHANGES since run-1.1.12-10
* Ensure stdout and stderr in inferior are distinct.
--
Charles Wilson
volunteer run maintainer for
2009/12/2 jeffunit:
My program ran fine under cygwin 1.5 as well as many versions of linux
including
mandriva 2009, mandriva 2009.1 and mandriva 2010.0
When compiled with
gcc cal.c -o cal
and run with
cal 2009
I get a segmentation fault.
When I uncomment line 62, the program runs
Andy Koppe wrote:
2009/12/2 jeffunit:
My program ran fine under cygwin 1.5 as well as many versions of linux
including
mandriva 2009, mandriva 2009.1 and mandriva 2010.0
When compiled with
gcc cal.c -o cal
and run with
cal 2009
I get a segmentation fault.
When I uncomment line 62, the
2009/12/2 Dave Korn:
Andy Koppe wrote:
2009/12/2 jeffunit:
My program ran fine under cygwin 1.5 as well as many versions of linux
including
mandriva 2009, mandriva 2009.1 and mandriva 2010.0
When compiled with
gcc cal.c -o cal
and run with
cal 2009
I get a segmentation fault.
When I
The run package provides a simple application to launch console programs
with their console hidden.
[[ compiled using gcc-3.4.4-999 ]]
CHANGES since run-1.1.12-1
* Ensure stdout and stderr in inferior are distinct.
--
Charles Wilson
volunteer run maintainer for
The run package provides a simple application to launch console programs
with their console hidden.
[[ compiled using gcc-4.3.4-1 ]]
CHANGES since run-1.1.12-10
* Ensure stdout and stderr in inferior are distinct.
--
Charles Wilson
volunteer run maintainer for
83 matches
Mail list logo
