From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [HEADSUP] New github organization "cygwin"
Date: Thu, 17 Mar 2016 16:33:00 -0000 [thread overview]
Message-ID: <20160317163302.GD24385@calimero.vinschen.de> (raw)
In-Reply-To: <56EAD570.1010405@cygwin.com>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On Mar 17 11:04, Yaakov Selkowitz wrote:
> On 2016-03-17 10:49, Corinna Vinschen wrote:
> >today I claimed the "cygwin" name at github.com. If you have some funny
> >project which is using Cygwin in the first place, and you want to do
> >that under the "cygwin" cover, feel free to drop us a mail here on
> >cygwin-apps and we add you as member. You can then create your own git
> >repo under this hood if you like. It should just be closely related to
> >Cygwin.
>
> cygwinports is an organization on github as well. It may make sense to
> leave packaging in cygwinports and original code in cygwin, since the repo
> names may otherwise conflict.
Sure. Cygwinports purpose is to provide ports of existing OSS projects.
The idea for "cygwin" is to be used for cygwin-specific project repos.
E. g., some nifty scripting which only makes sense in a Cygwin environment
might find a nice home there.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-17 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 15:49 Corinna Vinschen
2016-03-17 16:04 ` Yaakov Selkowitz
2016-03-17 16:33 ` Corinna Vinschen [this message]
2016-03-18 12:37 ` Adam Dinwoodie
2016-03-18 13:27 ` Corinna Vinschen
2016-03-18 17:49 ` Yaakov Selkowitz
2016-03-18 20:01 ` Corinna Vinschen
2016-03-18 21:00 ` Adam Dinwoodie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160317163302.GD24385@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).