On Oct 5 22:19, Karl M wrote:
Hi All...
What about calling it B21? :
*cough*
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:[EMAIL PROTECTED]
Red Hat, Inc.
--
Unsubscribe info:
Karl M schrieb:
What about calling it B21? :
As already discussed on cygwin-talk and as officially described on the
webpage, B stood for Beta that times (up to 1998).
We are already stable since a few years, though we use uneven version
numbers, marking it as developer releases.
fun
So we
On Tue, Oct 05, 2004 at 10:19:29PM -0700, Karl M wrote:
Hi All...
What about calling it B21? :
It's as good a name for vaporware as any.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
On Wed, Oct 06, 2004 at 02:47:15PM +0200, Reini Urban wrote:
Karl M schrieb:
What about calling it B21? :
As already discussed on cygwin-talk and as officially described on the
webpage, B stood for Beta that times (up to 1998).
We are already stable since a few years, though we use uneven
On Oct 6 11:09, Christopher Faylor wrote:
On Wed, Oct 06, 2004 at 02:47:15PM +0200, Reini Urban wrote:
Go with the Redhat scheme and use Cygwin 1.6.0.
Please don't do this. Red Hat is using the even numbers. I don't know
if there is already a 1.6.0 [...]
There is.
Corinna
--
Corinna
On Thu, 30 Sep 2004 22:31:26 -0700, David Christensen wrote:
Per the Cygwin FAQ (http://cygwin.com/faq.html):
If you are looking for the version number for the whole Cygwin
release, there is none. Each package in the Cygwin release has its own
version. The packages in Cygwin are
Hi All...
What about calling it B21? :
...
From: Joshua Daniel Franklin [EMAIL PROTECTED]
Reply-To: Joshua Daniel Franklin [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Request for a version/ revision/ release number for the whole
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf
Of David Christensen
Sent: Sunday, October 03, 2004 4:15 AM
To: [EMAIL PROTECTED]
Subject: RE: Request for a version/ revision/ release number for the
whole Cygwin release/ distribution
I don't
Mike Kenny - BCX - Infrastructure Services wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf
Of David Christensen
Sent: Sunday, October 03, 2004 4:15 AM
To: [EMAIL PROTECTED]
Subject: RE: Request for a version/ revision/ release number for the
whole Cygwin
-Original Message-
From: cygwin-owner On Behalf Of David Christensen
Sent: 03 October 2004 03:15
Would you be interested in mentoring a willing volunteer?
Certainly. Just stand still right here for just one minute
KER-SQUELCH-SPLAT-SMACK
[sound of
On Mon, 4 Oct 2004, Dave Korn wrote:
-Original Message-
From: cygwin-owner On Behalf Of David Christensen
Sent: 03 October 2004 03:15
Would you be interested in mentoring a willing volunteer?
Certainly. Just stand still right here for just one minute
-Original Message-
From: Igor Pechtchanski
Sent: 04 October 2004 15:31
I just felt that this sums up the whole volunteering bit
nicely. Though perhaps it's time to TITTTL...
Seconded!
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe
Christopher Faylor writes:
The total number of unique subscribers to cygwin, cygwin-apps,
cygwin-talk, cygwin-xfree is 2542.
That count may fall short by not taking into account those who read,
say, gmane.os.cygwin, but do not subscribe to the cygwin list.
--
Steven E. Harris
--
On Mon, 4 Oct 2004, Hughes, Bill wrote:
Igor Pechtchanski wrote:
On Mon, 4 Oct 2004, Dave Korn wrote:
..snip..
Certainly. Just stand still right here for just one minute
KER-SQUELCH-SPLAT-SMACK
[sound of massive slap round face with a very wet kipper]
On Mon, Oct 04, 2004 at 08:24:35AM -0700, Steven E. Harris wrote:
Christopher Faylor writes:
The total number of unique subscribers to cygwin, cygwin-apps,
cygwin-talk, cygwin-xfree is 2542.
That count may fall short by not taking into account those who read,
say, gmane.os.cygwin, but do not
On Sat, 2 Oct 2004, David Christensen wrote:
I disagree. Assume for a moment that all Cygwin project member
development efforts can be put into the following bins:
1. Code development.
2. Design documentation.
3. Test suite development.
4. Test suite documentation.
5. Test suite
Gary R. Van Sickle wrote:
How many people have heard The Two Rules of Customer Service?
1. The customer is always right.
The customer is indeed *NOT* always right but the trick is usually to
make them *think* there always right.
2. When the customer is wrong, refer to rule #1.
Everybody. How
-Original Message-
From: cygwin-owner On Behalf Of Andrew DeFaria
Sent: 04 October 2004 19:19
Gary R. Van Sickle wrote:
How many people have heard The Two Rules of Customer Service?
1. The customer is always right.
The customer is indeed *NOT* always right but the trick is
It would seem that bin #1 is consuming the majority of the effort. I
think that by changing priorities and re-allocating people and
resources, it should be possible to create integration tests and a
stable distribution. Such would increase Cygwin's acceptance and
usage for potentially
Corinna Vinschen wrote:
I'm one of the maintainers of the Cygwin DLL ... [and]
about 25 ported
software packages.
Creating a distribution ... is clearly the job for somebody else.
OK Corinna is very busy.
All people involved are very busy.
Jorg Schaible wrote:
Win XP Home SP2
Gary R. Van Sickle schrieb:
It would increase the amount of work application developers (assuming you
mean package maintainers) would have to do. More work for no pay has never
been welcomed by anybody in the history of the world.
Well, they only good reason to start such a project would be
On Sun, Oct 03, 2004 at 06:07:18PM +0200, Reini Urban wrote:
Well, the only good reason to start such a project would be monetary
benefits. Besides the simplification of having a (stable) cygwin
snapshot release from time to time, where all packages play well
together.
And I don't see any
On Sat, Oct 02, 2004 at 01:28:52PM -0500, Gary R. Van Sickle wrote:
[David Christensen wrote:]
Actually, I have already copied my Cygwin package tree to a
CD for installing on other computers. I need to review the
Cygwin license to see if a third-party distribution is allowed.
It's
Thank you for participating in this discussion. It may turn out to be an
important issue in the future--however, I think there may be a few general
concepts that have been used by participants in the discussion which
concepts' meanings are not the same by all participants. This message does
not
David Christensen wrote:
[EMAIL PROTECTED]:
Per the Cygwin FAQ (http://cygwin.com/faq.html):
If you are looking for the version number for the whole Cygwin
release, there is none. Each package in the Cygwin release has its own
version. The packages in Cygwin are continually improving,
[EMAIL PROTECTED]:
Thank you all for your replies thus far. I suspected that my posting
would generate traffic. :-)
I would especially like to request that there be a stable
distribution.
This wish was inspired by my positive experiences with Debian stable
-- e.g. feature frozen, unit and
On Sat, Oct 02, 2004 at 12:03:09AM -0700, David Christensen wrote:
cygwin mailing list address deleted
There is no reason to include the email address in your messages. That
just adds spam fodder to the archives.
p.s. I hereby volunteer my time to work on implementing my request.
I'm still
On Oct 1 05:08, Gary R. Van Sickle wrote:
1. Roll up your sleeves, get to work, and let the list know when
you're done. The maintainers (yes, I'm looking at you
Chris) will
at best see this as a threat to their little fifedom, and the only
help you'll get will be in the form of
[EMAIL PROTECTED]:
Thank you all for your replies thus far. I suspected that my
posting would generate traffic. :-)
I would especially like to request that there be a stable
distribution.
This wish was inspired by my positive experiences with Debian stable
-- e.g. feature
David Christensen wrote:
This wish was inspired by my positive experiences with Debian stable
-- e.g. feature frozen, unit and integration tested, with updates
limited to bug and security fixes.
Please note that Debian is a volunteer effort:
http://www.debian.org/devel/join/
On Sat, Oct 02, 2004 at 12:03:02PM -0700, Brian Dessent wrote:
David Christensen wrote:
This wish was inspired by my positive experiences with Debian stable
-- e.g. feature frozen, unit and integration tested, with updates
limited to bug and security fixes.
Please note that Debian is a volunteer
Gary R. Van Sickle wrote:
No, test development should be done by people not involved with the
development of the software under test, or you have a conflict of interest.
Not entirely true. There's whitebox testing -- where knowledge of
internals is used to craft the test; this is often done by
Gary R. Van Sickle wrote:
No, test development should be done by people not involved with the
development of the software under test, or you have a
conflict of interest.
Not entirely true. There's whitebox testing -- where
knowledge of internals is used to craft the test; this is
Thank you all for your comments. I have tried to respond to each person
who replied, but may have omitted those where their topic is already
covered below.
Corinna Vinschen wrote:
I'm one of the maintainers of the Cygwin DLL ... [and] about 25
ported software packages.
Creating a
On Sat, 2 Oct 2004, David Christensen wrote:
Thank you all for your comments. I have tried to respond to each person
who replied, but may have omitted those where their topic is already
covered below.
[snip]
Dave Korn wrote:
http://cygwin.com/acronyms#PCYMTNQREAIYR
Is there a way to do
On Sun, Oct 03, 2004 at 12:09:24AM -0400, Igor Pechtchanski wrote:
On Sat, 2 Oct 2004, David Christensen wrote:
Thank you all for your comments. I have tried to respond to each person
who replied, but may have omitted those where their topic is already
covered below.
[snip]
Dave Korn
David Christensen wrote:
If we can build a fully automated Cygwin stable test suite and
parallelize it across many computers (wishful thinking: SETI screen
saver), it may be possible to do 100% testing of all changes prior to
release -- major, minor, and updates.
Fortunately for all the
On Sat, Oct 02, 2004 at 09:49:29PM -0700, Brian Dessent wrote:
David Christensen wrote:
If we can build a fully automated Cygwin stable test suite and
parallelize it across many computers (wishful thinking: SETI screen
saver), it may be possible to do 100% testing of all changes prior to
I would like to request that this policy be reversed -- that
there be a version number for the entire Cygwin release.
Every O/S and application I've used had a release number for
the whole thing; Cygwin should as well.
I would especially like to request that there be a stable
David Christensen wrote:
[EMAIL PROTECTED]:
Per the Cygwin FAQ (http://cygwin.com/faq.html):
If you are looking for the version number for the whole Cygwin
release, there is none. Each package in the Cygwin release has its own
version. The packages in Cygwin are continually improving, thanks to
-Original Message-
From: cygwin-owner On Behalf Of David Christensen
Sent: 01 October 2004 06:31
[EMAIL PROTECTED]:
http://cygwin.com/acronyms#PCYMTNQREAIYR, then please don't go and manually
enter any either!
Per the Cygwin FAQ (http://cygwin.com/faq.html):
If you are
On Oct 1 14:16, Dave Korn wrote:
Or you can take option b), and pay someone to do this work for you: I'm
sure Red Hat would still be glad to discuss terms for Cygwin support contracts.
Absolutely.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin
On Thu, Sep 30, 2004 at 10:31:26PM -0700, David Christensen wrote:
cygwin blah..
http://cygwin.com/acronyms/#PCYMTNQREAIYR
Per the Cygwin FAQ (http://cygwin.com/faq.html):
If you are looking for the version number for the whole Cygwin
release, there is none. Each package in the Cygwin release
On 10/01/2004 at 12:31:34 AM, [EMAIL PROTECTED] wrote:
Every O/S and application
I've used had a release number for the whole thing; Cygwin should as
well.
--- end of excerpt ---
At a minimum, I think that's quite an oversimplification and perhaps
factually untrue?
Have you used a Linux
-Original Message-
From: cygwin-owner On Behalf Of Christopher Faylor
Sent: 01 October 2004 17:24
This assumes that somehow the cron-2.6.2 EOF issue (I'm not familiar
with this and don't recall seeing it mentioned here)
He meant rsync, not cron, and he meant EOL, not EOF, but
On Fri, Oct 01, 2004 at 11:52:15AM -0500, Fred Kulack wrote:
On 10/01/2004 at 12:31:34 AM, cygwin-owner wrote:
Every O/S and application I've used had a release number for the whole
thing; Cygwin should as well.
--- end of excerpt ---
At a minimum, I think that's quite an oversimplification and
On Fri, Oct 01, 2004 at 01:15:25PM -0400, Christopher Faylor wrote:
As I said, I very am familiar with the effort that goes into releasing
am very
cgf
(who only sees these things after hitting 'y' or when perusing the archives
months later...)
--
Unsubscribe info:
For what it's worth, I'm at this very moment moving my company's build
system away from Cygwin, for precisely reason number 4: I cannot tell
customers which Cygwin version to get.
--
The one thing that unites all human beings, regardless of age,
gender, religion, economic status or ethnic
On Fri, Oct 01, 2004 at 01:22:56 -0400, Christopher Faylor wrote:
On Fri, Oct 01, 2004 at 01:15:25PM -0400, Christopher Faylor wrote:
As I said, I very am familiar with the effort that goes into releasing
am very
cgf
(who only sees these things after hitting 'y' or when
On Fri, Oct 01, 2004 at 04:54:36PM -0400, Igor Pechtchanski wrote:
On Fri, Oct 01, 2004 at 01:22:56 -0400, Christopher Faylor wrote:
On Fri, Oct 01, 2004 at 01:15:25PM -0400, Christopher Faylor wrote:
As I said, I very am familiar with the effort that goes into releasing
am very
On Fri, 1 Oct 2004, Eric Hanchrow wrote:
For what it's worth, I'm at this very moment moving my company's build
system away from Cygwin, for precisely reason number 4: I cannot tell
customers which Cygwin version to get.
Stock answer: use what's current
Cygwin is an ever-changing project and
On Fri, 1 Oct 2004, Christopher Faylor wrote:
On Fri, Oct 01, 2004 at 04:54:36PM -0400, Igor Pechtchanski wrote:
On Fri, Oct 01, 2004 at 01:22:56 -0400, Christopher Faylor wrote:
On Fri, Oct 01, 2004 at 01:15:25PM -0400, Christopher Faylor wrote:
As I said, I very am familiar with the
Peter A. Castro wrote:
to keep up with the flow. Yes, it may be a little painful if you haven't
refreshed in a while (say, from the b20 days :), but you will have
Ah. Cygwin B20.1. Man, those were the days. Cygwin was practically
perfect in every way, bugfree, and featureful. It even made
On Fri, Oct 01, 2004 at 06:05:06PM -0400, Charles Wilson wrote:
Peter A. Castro wrote:
to keep up with the flow. Yes, it may be a little painful if you
haven't refreshed in a while (say, from the b20 days :), but you will
have
Ah. Cygwin B20.1. Man, those were the days. Cygwin was practically
[EMAIL PROTECTED]:
Per the Cygwin FAQ (http://cygwin.com/faq.html):
If you are looking for the version number for the whole Cygwin
release, there is none. Each package in the Cygwin release has its own
version. The packages in Cygwin are continually improving, thanks to the
efforts of
55 matches
Mail list logo
