DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=ly
	L9mwAg3Udlbzgstp/F2XU17uWYoWT9bjbmdAIbmAabz/3qFcWVhu4+C2HVdJbGBE
	GI38P6vD+igMDcJJI4DsBdMEE0ZnnwNxRG4KtzVjGZXKkNdVE0pugarjn6yGaaqb
	T3mZztpTbE9NuWMIJQGPYRNIRo+m9voAQQUlZ5eWU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <20140123130823.GB7177@ednor.casa.cgf.cx>
References: <CAO2ddnbtJ_mY1Yei6cx2GQO1dAWv=OV-cDVFO+aZD935MGQ7mA@mail.gmail.com>	<20140122023112.GA4286@ednor.casa.cgf.cx>	<CAO2ddnZM2FwzUSBJ2WHrBpQMe1sDt-8rWBpdJHEEzH3XCh3x4g@mail.gmail.com>	<20140122180852.GA3153@ednor.casa.cgf.cx>	<CAO2ddnaWAa0eeQZFQCEHzY+r2V75P1nnmW02fUeWLXsOuvzV1Q@mail.gmail.com>	<20140123130823.GB7177@ednor.casa.cgf.cx>
Date: Thu, 23 Jan 2014 16:35:47 +0100
Message-ID: <CAO2ddnbXX_556nv8dsUXDc1UNSCpmRoKjC6Su1GDW_NptiHQyQ@mail.gmail.com>
Subject: Re: AdminCygwin Release
From: BGINFO4X <bginfo4x@kztsoftware.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1

>>> You're actually treading on thin ice here since you are trying to get
>>> help for a release that is not the subject of this mailing list.  That
>>> makes this whole discussion pretty much off-topic.
>>
>>Yes, I'm sorry. I will move the discussion to cygwin-talk list if you
>>don't mind.
>
> Actually, I do mind.  The cygwin-talk list isn't intended to be a forum
> to discuss other cygwin releases.

Well, is there any cygwin-list to talk about this?

>>> And that's another issue.  We definitely will not be providing support
>>> for anyone who wanders in here looking for help with problems they
>>> encounter with your packages.
>>
>>I TOTALLY agree with this.
>
> You may agree with this but that won't stop people from being confused.

> I still think this is a bad idea.  I know what you're trying to do.  You
> are basically trying to provide a solution using tools that you more or
> less understand rather than trying to work within the existing
> (admittedly crude) release structure to provide benefit to everyone who
> uses Cygwin.

I'm sorry, but this is not true: I only want to give comunity a "base
package" of something that I already have.

At least on my opinion, as an administrator, has very sense to have a
"bash windows" in a "nerd-msi" installable form.

But if you don't agree, don't mind: I can upload my next BGINFO4X
release without creating any "AdminCygwin release".

There is no problem, but I thought that it could be useful to others.

> We sometimes get people here who think they have to fork Cygwin because
> they understand some subset of something on their own and don't or can't
> grok the big picture well enough to try to make changes within the
> release.  There is that + the need some people have of being a
> recognized "Project lead".  Believe me, the glory in that title cannot
> be underestimated.  It's a heady experience.

I'm sorry again, but If I understand you (not 100% sure), I don't want
to be recognized.

Thanks a lot for your time.

> cgf
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple