I will definitely stop by. Looking forward to meeting all the Sage
people.
On Oct 14, 8:32 pm, mhampton wrote:
> I started a wiki page for this:
>
> http://wiki.sagemath.org/jmms2010
>
> and I took the liberty of adding Karl, Rob Beezer, and William as
> participants. Hopefully that's OK. I en
Hi,
I. SAGE-4.1.2: Sage-4.1.2 has been released.
1. You can download the source code here:
http://sage.math.washington.edu/sage/src/sage-4.1.2.tar
2. I've posted many binaries here:
http://sage.math.washington.edu/home/wstein/binaries/
(not, a few are still being
Hello,
On Thu, Oct 15, 2009 at 12:13 PM, Bill Hart wrote:
>
> I've just put up MPIR 1.3 (alpha) for testing.
>
> As there is sooo much new code there is a very real possibility that
> the Sage test suite will turn something up. Any volunteers to make an
> spkg and see?
I have an spkg up at
http
I've just put up MPIR 1.3 (alpha) for testing.
As there is sooo much new code there is a very real possibility that
the Sage test suite will turn something up. Any volunteers to make an
spkg and see?
We especially would appreciate owners of Apple machines and anything
slightly exotic, to test MP
On Oct 14, 2009, at 7:09 AM, kcrisman wrote:
>>> I don't think this would work at all, unless there is an *easy*
>>> automated procedure to submit a patch to a bot which (a) applies the
>>> patch to the current tree (b) compiles in all platforms (c) attaches
>>> the logs to the ticket and possibl
On Oct 14, 2009, at 5:27 AM, Gonzalo Tornaria wrote:
> On Wed, Oct 14, 2009 at 6:49 AM, Burcin Erocal
> wrote:
>> The status of "lieutenant" is the equivalent of having "commit
>> access"
>> in other open source projects. I would prefer a different term for
>> "lieutenant", but I don't have
A while back, I mentioned on sage-marketing the idea of making "Burma
Sage" advertisements for the Joint Meetings or some similar event.
(For those who don't know about Burma Shave advertisements: [1])
I made up some examples. :)
Why Sage and you
are a good match:
"Just implement it
and send us
I started a wiki page for this:
http://wiki.sagemath.org/jmms2010
and I took the liberty of adding Karl, Rob Beezer, and William as
participants. Hopefully that's OK. I encourage anyone else who is
attending to add your name to the list, since it will give me a better
idea of how many business
Thanks for the screencast, Minh. Uploading files now.
- Luis V. -
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options,
Hi,
Last night I switched the full http://sagenb.org over to use the new
separate-from-Sage Sage notebook code.In particular, this involves
using code for which the evaluation and storage code has been
rewritten. I'm curious how it is working for people/courses/whatever.
If you use http:
On Wed, Oct 14, 2009 at 4:43 PM, Ralf Hemmecke wrote:
>
>>> * To develop sage, one downloads the sourc tarball and then develops
>>> inside the devel/sage-xyz directory.
>>
>> No, this is wrong. You can *definitely* develop sage by downloading
>> a binary and extracting it. To modify the "sag
I've just added
http://trac.sagemath.org/sage_trac/ticket/6517#comment:17 (and 18)
Could someone please test this?
Thank
Ralf
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
>
> I can almost see several people sitting out in the lobby on a couch,
> with the huge Sage banner draped over your laps and hanging down in
> front of the couch, coding and having a great time.
But it won't be a party without you! We really need to get a head
count...
- kcrisman
--~--~
On Oct 14, 4:26 pm, Ralf Hemmecke wrote:
> On 10/15/2009 12:51 AM, John H Palmieri wrote:
>
> > On Oct 14, 3:15 pm, William Stein wrote:
> >> On Wed, Oct 14, 2009 at 12:56 PM, Ralf Hemmecke wrote:
>
> > [snip]
>
> >>> * There is no repository for the source code (i.e. source tarball minus
> >>>
>> * To develop sage, one downloads the sourc tarball and then develops
>> inside the devel/sage-xyz directory.
>
> No, this is wrong.You can *definitely* develop sage by downloading
> a binary and extracting it. To modify the "sage Python library"
> involves working on devel/sage-xyz.
Well
On 10/15/2009 12:51 AM, John H Palmieri wrote:
> On Oct 14, 3:15 pm, William Stein wrote:
>> On Wed, Oct 14, 2009 at 12:56 PM, Ralf Hemmecke wrote:
>
> [snip]
>
>>> * There is no repository for the source code (i.e. source tarball minus
>>> the directories spkg, devel, data, examples, local, (
On Oct 14, 3:15 pm, William Stein wrote:
> On Wed, Oct 14, 2009 at 12:56 PM, Ralf Hemmecke wrote:
[snip]
> > * There is no repository for the source code (i.e. source tarball minus
> > the directories spkg, devel, data, examples, local, (ipython).
>
> No, this is wrong. There is a repository
That would be great if you could do the stickers, and I will do the
business cards.
Thanks!
Marshall
On Oct 14, 2:37 pm, Rob Beezer wrote:
> I'll take on the sticker project if Marshall is looking to distribute
> the work. Maverick Label looks comparable in price with a slightly
> more idiot-p
On Wed, Oct 14, 2009 at 12:56 PM, Ralf Hemmecke wrote:
>
>>> Sage *is* different than other programs, since even in the binary
>>> release it comes with .hg repositories (under devel and local/bin) and
>>> lets users actually modify what they want.
>
>> Sage is indeed different in that the techno
ma...@mendelu.cz wrote:
> Do not know if this is relevant, but I get the message
> It looks like jsMath failed to set up properly (error code -7). I
> will try to keep going, but it could get ugly.
> when looking at published worksheets, like http://uw.sagenb.org/home/pub/4/
>
> I do not have th
On Wed, Oct 14, 2009 at 12:56 PM, Ralf Hemmecke wrote:
>
>>> Sage *is* different than other programs, since even in the binary
>>> release it comes with .hg repositories (under devel and local/bin) and
>>> lets users actually modify what they want.
>
>> Sage is indeed different in that the techno
Rob Beezer wrote:
> I'll take on the sticker project if Marshall is looking to distribute
> the work. Maverick Label looks comparable in price with a slightly
> more idiot-proof ordering interface (at a cost of fewer colors, I
> think). 500 might be overkill, but the marginal cost of the last 10
Do not know if this is relevant, but I get the message
It looks like jsMath failed to set up properly (error code -7). I
will try to keep going, but it could get ugly.
when looking at published worksheets, like http://uw.sagenb.org/home/pub/4/
I do not have this problem with Sage 4.1.1
Firefox
I'll take on the sticker project if Marshall is looking to distribute
the work. Maverick Label looks comparable in price with a slightly
more idiot-proof ordering interface (at a cost of fewer colors, I
think). 500 might be overkill, but the marginal cost of the last 100
stickers is 2.5 cents/st
William Stein a écrit :
> On Wed, Oct 14, 2009 at 4:55 AM, Thierry Dumont
> wrote:
>> W
>> 2) With the current notebook. I tried the following experience: I have 2
>> machines (actually 3). On these machines there are unix users sage1,
>> sage2, ..., sage3...,sagen, with the same uid and same gid
>> Sage *is* different than other programs, since even in the binary
>> release it comes with .hg repositories (under devel and local/bin) and
>> lets users actually modify what they want.
> Sage is indeed different in that the technology is constructed to
> discourage to "developer"/"end user"
> What is meant by "slow" ? Why should looking for the smallest integer not in
> the graph be "slow" ?
"Slow" means linear, not constant, for the obvious reasons.
> Is there any good reason why the function g.add_vertex does not return the
> name of the newly created vertex ?
Because it gets *r
I've been thinking about going to the joint meetings, and (although it
looks irrelevant) I still have the Sage banner in my office at UW.
On Wed, Oct 14, 2009 at 8:37 AM, William Stein wrote:
>
> On Tue, Oct 13, 2009 at 10:46 PM, Rob Beezer wrote:
>>
>> Marshall,
>>
>> Limited Googling got me:
On Wed, Oct 14, 2009 at 6:43 PM, William Stein wrote:
> I do not see it on any of my 20 or so clean builds. Maybe it arises
> only from an upgrade or something.
I did it from a clean build of 4.1.2.rc2.
--
Carlo Hamalainen
http://carlo-hamalainen.net
--~--~-~--~~~
On Wed, Oct 14, 2009 at 10:07 AM, Jason Grout
wrote:
>
> William Stein wrote:
>
>> I hope soon we'll have a web-based interface that allows one to easily
>> change Sage code using Bespin (that code editor), make patches, test
>> changes (on 10 platforms), etc., all trivially from a web browser vi
On Wed, Oct 14, 2009 at 3:09 AM, Juanjo
wrote:
>
> On Oct 11, 7:53 pm, William Stein wrote:
>> I was reading theeclbinaries and grepping around (I felt a bit like
>> a "warez person" for a moment)... and found this in the binary:
>>
>> ... ecld...@cannot findECL'sdirectory^...
>>
>> So I tri
William Stein wrote:
> I hope soon we'll have a web-based interface that allows one to easily
> change Sage code using Bespin (that code editor), make patches, test
> changes (on 10 platforms), etc., all trivially from a web browser via
> a webapp.
What do you mean by "hope soon":
1. People ar
On Wed, Oct 14, 2009 at 3:29 AM, Martin Albrecht
wrote:
>
> Hi there,
>
> I had trouble building the current rc2.
>
> make[6]: Leaving directory
> `/usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/src/library/base'
> /usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/bin/exec/R:
> /usr/local/sage-4
On Wed, Oct 14, 2009 at 4:09 AM, Tim Joseph Dumol wrote:
> I've worked on some Nginx servers using FCGI, so I can try.
Excellent. Write to me offlist with a requested login name for
sage.math.washington.edu, and I'll set things up so you can login to
the virtual machine that hosts trac.
Willia
On Wed, Oct 14, 2009 at 4:55 AM, Thierry Dumont
wrote:
> William Stein a écrit :
>> Hi,
>>
>> Nearly two weeks ago I had the notebook stabilized and all known new
>> bugs fixed (after separating it off from sage as a separate program
>> and rewriting the expect stuff). But I realized that it wou
On Wed, Oct 14, 2009 at 1:35 AM, Ralf Hemmecke wrote:
>
>> There has to be a significant benefit.
>
> I don't think that the idea of "configure" is/was that it is easier for
> the enduser. It's easier for the developers with only a very small
> overhead for the enduser. If something fails, an ord
On Wed, Oct 14, 2009 at 4:21 AM, Marshall Hampton wrote:
>
> I had the same error as Carlo, which I reported for the alpha4 and rc0
> releases as well. I'm sort of puzzled, given the nature of the error,
> as to why more people don't see it.
I do not see it on any of my 20 or so clean builds.
On Wed, Oct 14, 2009 at 2:12 AM, Dr. David Kirkby
wrote:
> 2) When submitting a patch, they attach logs showing building on all
> platforms, *except* the one they normally work on, since one can assume
> they have probably got their patch working there.
>
> This really is no more than an extensio
On Oct 14, 11:22 am, Minh Nguyen wrote:
> Hi kcrisman,
>
> On Thu, Oct 15, 2009 at 2:16 AM, kcrisman wrote:
>
>
>
> > Nope, I think we start with Tiger (10.4). In fact, definitely won't
> > work with the fix for dynamic links or whatever we did for cliquer.
> > I'm hoping to hang on to this
On Tue, Oct 13, 2009 at 10:46 PM, Rob Beezer wrote:
>
> Marshall,
>
> Limited Googling got me: http://www.sheet-labels.com/printing/
>
> $35 for 500 stickers at 1" x 0.625" which was the smallest I could
> find. Lots of options - rounded corners, different sizes, etc.
>
> Rob
I can certainly c
On Tue, Oct 13, 2009 at 10:46 PM, Rob Beezer wrote:
>
> Marshall,
>
> Limited Googling got me: http://www.sheet-labels.com/printing/
>
> $35 for 500 stickers at 1" x 0.625" which was the smallest I could
> find. Lots of options - rounded corners, different sizes, etc.
>
> Rob
I asked my brothe
Hi kcrisman,
On Thu, Oct 15, 2009 at 2:16 AM, kcrisman wrote:
> Nope, I think we start with Tiger (10.4). In fact, definitely won't
> work with the fix for dynamic links or whatever we did for cliquer.
> I'm hoping to hang on to this one for a little longer for the same
> purpose, but we'll
Hi David,
On Thu, Oct 15, 2009 at 1:43 AM, Dr. David Kirkby
wrote:
> Setting up such a build-bot is not something I have ever attempted. I
> would imagine is quite a bit of work to get it right.
Indeed it does when one considers that a build-bot would need to
initiate a build of an alpha, rc
On Oct 14, 10:45 am, Jason Grout wrote:
> kcrisman wrote:
>
> >>> I don't think this would work at all, unless there is an *easy*
> >>> automated procedure to submit a patch to a bot which (a) applies the
> >>> patch to the current tree (b) compiles in all platforms (c) attaches
> >>> the logs
kcrisman wrote:
>
>
>>> I don't think this would work at all, unless there is an *easy*
>>> automated procedure to submit a patch to a bot which (a) applies the
>>> patch to the current tree (b) compiles in all platforms (c) attaches
>>> the logs to the ticket and possibly flags the ticket depen
kcrisman wrote:
>
> Fascinating discussion.
>
> I just want to emphasize two things as a representative of those who
> knew virtually nothing about programming or open source when we
> started.
>
> 1) If you're serious about this doctesting (esp. on different
> platforms) thing, there has to be
On Oct 14, 9:33 am, Minh Nguyen wrote:
> Hi kcrisman,
>
> On Thu, Oct 15, 2009 at 12:25 AM, kcrisman wrote:
>
>
>
> > My point
> > was that neither of them correspond to the list of blockers on the
> > "official" milestone page, and that page doesn't have any clues as to
> > what filter was u
> > I don't think this would work at all, unless there is an *easy*
> > automated procedure to submit a patch to a bot which (a) applies the
> > patch to the current tree (b) compiles in all platforms (c) attaches
> > the logs to the ticket and possibly flags the ticket depending on the
> > resu
Gonzalo Tornaria wrote:
> On Wed, Oct 14, 2009 at 7:12 AM, Dr. David Kirkby
> wrote:
>> 2) When submitting a patch, they attach logs showing building on all
>> platforms, *except* the one they normally work on, since one can assume
>> they have probably got their patch working there.
>
> I don't
Fascinating discussion.
I just want to emphasize two things as a representative of those who
knew virtually nothing about programming or open source when we
started.
1) If you're serious about this doctesting (esp. on different
platforms) thing, there has to be a way to make it drop-dead easy -
Gonzalo Tornaria wrote:
> What compiler will be used if gcc and g++ are not in the path?
> Presumably, this will only work if CC and CXX are set to proper
> compilers, right? Doesn't it make sense to:
> 4) check for gcc and g++ except when CC and/or CXX are set, in
> which case, check for CC
Hi kcrisman,
On Thu, Oct 15, 2009 at 12:25 AM, kcrisman wrote:
> My point
> was that neither of them correspond to the list of blockers on the
> "official" milestone page, and that page doesn't have any clues as to
> what filter was used to generate it.
I was the person who edited the Sage 4
On Oct 14, 9:00 am, Minh Nguyen wrote:
> Hi kcrisman,
>
> On Wed, Oct 14, 2009 at 11:51 PM, kcrisman wrote:
>
> > This may be a dumb question, but...
>
> > Why doesn'thttp://trac.sagemath.org/sage_trac/milestone/sage-4.1.2
> > agree with
> >http://trac.sagemath.org/sage_trac/query?status=assig
On Wed, Oct 14, 2009 at 10:06 AM, Dr. David Kirkby
wrote:
> ---
> 3) Exit if gcc or g++ can not be found unless SAGE_PORT is exported to
> some non-empty value. Currently SAGE_PORT is only needed on some
> operating systems, and has nothing to do with compilers, bu
On Wed, Oct 14, 2009 at 7:12 AM, Dr. David Kirkby
wrote:
> 2) When submitting a patch, they attach logs showing building on all
> platforms, *except* the one they normally work on, since one can assume
> they have probably got their patch working there.
I don't think this would work at all, unle
> >> 2) On HP-UX, the configure script can't work out how many CPUs I have,
> >> what sort they are, but then tries to determine the cache size. This
> >> causes the configure script to break.
> >>
> >> The macro for determining the number of CPUs
> >>
> >> http://git.savannah.gnu.org/gitweb/?p=au
Hi kcrisman,
On Wed, Oct 14, 2009 at 11:51 PM, kcrisman wrote:
>
> This may be a dumb question, but...
>
> Why doesn't http://trac.sagemath.org/sage_trac/milestone/sage-4.1.2
> agree with
> http://trac.sagemath.org/sage_trac/query?status=assigned&status=new&status=reopened&group=status&order=prio
Martin Albrecht wrote:
> On Wednesday 14 October 2009, Dr. David Kirkby wrote:
>> libm4ri has two issues that I am aware of as soon as one tries to use a
>> non-GNU or non-86 environment.
>>
>>
>> I believe the developers hang out here, so I'll put a bit of information
>> here, on the hope they se
This may be a dumb question, but...
Why doesn't http://trac.sagemath.org/sage_trac/milestone/sage-4.1.2
agree with
http://trac.sagemath.org/sage_trac/query?status=assigned&status=new&status=reopened&group=status&order=priority&priority=blocker&col=id&col=summary&col=priority&col=owner&col=type&co
On Wed, Oct 14, 2009 at 6:49 AM, Burcin Erocal wrote:
> The status of "lieutenant" is the equivalent of having "commit access"
> in other open source projects. I would prefer a different term for
> "lieutenant", but I don't have anything better now.
What about "editor"?
Gonzalo
--~--~-
Hi folks,
On Wed, Oct 14, 2009 at 2:38 AM, William Stein wrote:
>
> Hi,
>
> This is a release candidate for Sage-4.1.2:
>
> http://sage.math.washington.edu/home/wstein/farm/src/sage-4.1.2.rc2.tar
In case anyone is interested, here's the HTML version of this
version's standard documentation:
ht
On Oct 14, 1:30 pm, gsw wrote:
> How about intertwining these two phases?
i don't know how manageable this is, especially when patches depend on
each other and so on.
a similar approach would be to have a main trunk, like an inifite
alpha, and from time to time a second release manager picks
On Wed, Oct 14, 2009 at 04:09, William Stein wrote:
> In many talks, etc., I have made a big stink about how every released
> version of Sage is available, ...
The way to go is to go to the front page, click on "source" (below download)
and then on "older version". I made the later one a bit bi
gsw wrote:
>
> +1 to option (3).
>
> Cheers, Georg
OK, give there are two +1's, I also think option 3 is best, then when I
make a new prereq, the following will happen. (option 3)
---
3) Exit if gcc or g++ can not be found unless SAGE_PORT is exported to
some
William Stein a écrit :
> Hi,
>
> Nearly two weeks ago I had the notebook stabilized and all known new
> bugs fixed (after separating it off from sage as a separate program
> and rewriting the expect stuff). But I realized that it would be a
> total nightmare to introduce yet another sobj ("sage
Hi,
there's another possibility to speed up the Sage release frequency, by
a certain parallelization.
Currently, the Sage releases are done sequentially, and in two phases:
- the "alpha" phase, where tons of tickets are merged, and new
functionality gets in
- the "release cadidate" phase, where
I had the same error as Carlo, which I reported for the alpha4 and rc0
releases as well. I'm sort of puzzled, given the nature of the error,
as to why more people don't see it.
I also had
sage -t "devel/sage/doc/en/bordeaux_2008/birds_other.rst"
A mysterious error (perhaps a memory error?) occ
I've worked on some Nginx servers using FCGI, so I can try.
On Wed, Oct 14, 2009 at 5:21 AM, William Stein wrote:
>
> Hi,
>
> Currently I think trac.sagemath.org is setup to use the default
> builtin Python webserver. This sucks performance wise. I discovered
> that Microsoft's MSN search eng
On Oct 14, 7:28 am, Rob Beezer wrote:
> I wonder if the "lieutenant" model used by Linux kernel development
> might be helpful here?
Ok, I've read this and to make sure you all are not talking about
different things: there are two ways to split the workload:
- horizontally: Sage itself is spl
+1 to option (3).
Cheers, Georg
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.
Hi there,
I had trouble building the current rc2.
make[6]: Leaving directory
`/usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/src/library/base'
/usr/local/sage-4.1.2.rc2/spkg/build/r-2.9.2/src/bin/exec/R:
/usr/local/sage-4.1.2.rc2/local/lib/gcc-lib/x86_64-unknown-linux-
gnu/4.0.3/libgcc_s.so.
On Tue, Oct 13, 2009 at 5:38 PM, William Stein wrote:
> This is a release candidate for Sage-4.1.2:
>
> http://sage.math.washington.edu/home/wstein/farm/src/sage-4.1.2.rc2.tar
sage -testall reported just one failure on Ubuntu 9.04 x86 32bit:
$ sage -t "devel/sage/sage/server/notebook/cell.py"
On Oct 11, 7:53 pm, William Stein wrote:
> I was reading theeclbinaries and grepping around (I felt a bit like
> a "warez person" for a moment)... and found this in the binary:
>
> ... ecld...@cannot findECL'sdirectory^...
>
> So I tried setting ECLDIR, and that fixes the problem. Maybe we j
On Wednesday 14 October 2009, Dr. David Kirkby wrote:
> libm4ri has two issues that I am aware of as soon as one tries to use a
> non-GNU or non-86 environment.
>
>
> I believe the developers hang out here, so I'll put a bit of information
> here, on the hope they see it.
>
> 1) Despite the fac
Hi!
Part of the problem seems money. IIRC there is some funding by Google
and by Sun. Can this be used to pay release management?
On Oct 14, 6:28 am, Rob Beezer wrote:
> [...]
> I wonder if the "lieutenant" model used by Linux kernel development
> might be helpful here? If there was one or two
William Stein wrote:
> I think a huge amount of the problem will be that many of those 66
> positive reviewed tickets probably will:
> (2) many of the patches will probably fail on 32-bit or ppc or OS X,
> even though they worked fine on sage.math.
In a post yesterday I said:
---
> I don't know how much we can count on distutils/distribute/scons/? to
> support non-gnu toolchains. On the other hand, if we're just using
> pure Python, then I agree that it would lend itself to a much cleaner
> build system (though then we risk re-inventing the wheel...)
Maybe somebody
> My perspective on Ralf's proposal is not to rewrite anything we
> currently do, but to make it so building Sage feels "standard". I.e.,
> when I download some random tarball off the web, if it is a C/C++
> program I 100% expect that:
>
> ./configure --prefix=/usr/local/ # say
> mak
Hi,
On Tue, 13 Oct 2009 23:21:37 -0700
William Stein wrote:
> What is "release management"?Right now there are *66* tickets
> listed as "positive review" right here:
>http://trac.sagemath.org/sage_trac/report/11
>
> Definition: Release management is the process of taking th
> There has to be a significant benefit.
I don't think that the idea of "configure" is/was that it is easier for
the enduser. It's easier for the developers with only a very small
overhead for the enduser. If something fails, an ordinary enduser
probably has no idea what to do next. This appli
>> Just generating the toplevel makefile (and perhaps sage-env) should be
>> easy. But you probably also mean spkg/install and spkg/standard/deps. If
>> these would be the only files (in a first round) that would be doable.
>> Have I forgotten anything?
> I think creating the spkg-installs wou
> I would prefer avoiding autoconf completely for this unless there is a
> very compelling reason to do otherwise. I see no need for it at all.
> It's one thing to have a familiar shell scripts called "configure",
> and another to use autoconf.
Why not use tools (on the developer side) that supp
> I'm not saying the top level configure script needs to be created by
> autoconf, though it would look more 'normal' if it was, as 95% of
> 'configure' scripts are created using autoconf.
As usual, autoconf/automake are only required on the developer side.
Programs are usually distributed wit
Hello,
On Wed, Oct 14, 2009 at 1:21 PM, William Stein wrote:
> Definition: Release management is the process of taking these tickets,
> applying them, bouncing those that don't work, creating a sage-4.2.tar
> that works on our supported platforms, and creating binaries. If an
> unacceptable nu
84 matches
Mail list logo
