Message-id: <4E644629.1010005@cygwin.com>
Date: Sun, 04 Sep 2011 23:46:49 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: More on Cygwin package naming
References: <4E643ED8 DOT 3030100 AT cisra DOT canon DOT com DOT au>
In-reply-to: <4E643ED8.3030100@cisra.canon.com.au>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On 9/4/2011 11:15 PM, Luke Kendall wrote:
> It would be /nice/ if someone could confirm that the upstream project name
> is used for the @-names, or at least that cygwin does not use any existing
> Freshmeat project name and apply it to different software.

FWIW, I think it's fair to say that there is a convention of using the
upstream project name for the @-names.  But as with all conventions, there
are variations used when called for.  I think it's fair to say that the
last part of your statement is true but I also couldn't guarantee that it
will always be.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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