public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: "newlib@sourceware.org" <newlib@sourceware.org>,
	"cygwin-developers@cygwin.com" <cygwin-developers@cygwin.com>
Subject: Re: Evil deed: Switching development repository to git
Date: Thu, 05 Mar 2015 15:59:00 -0000	[thread overview]
Message-ID: <20150305155939.GH3213@calimero.vinschen.de> (raw)
In-Reply-To: <F2C22140-82E0-470B-9F87-9DC45503CA9C@oarcorp.com>

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

Hi Joel,

On Mar  5 09:32, Joel Sherrill wrote:
> 
> 
> On March 5, 2015 8:55:41 AM CST, Corinna Vinschen <vinschen@redhat.com> wrote:
> >Hi folks,
> >
> >
> >next week, I'm planning to move the combined newlib/libgloss and cygwin
> >repository from CVS to git.  The basic stuff is quickly done, but
> >hooks,
> >mailing list handling, and changes to the websites are to be done, so I
> >expect the switch to take about two days.
> >
> >I'll set up a commit moratorium starting next Monday at about 10:00
> >UTC.
> >
> >When the git repo is up and working I'll throw the lever and inform the
> >mailing lists.  Afterwards you can expect to access the new combined
> >newlib/cygwin git repository via either
> >
> >  git clone git://sourceware.org/git/newlib-cygwin.git
> >
> >or, if you have write permissions on the repo
> >
> >  git clone sourceware.org:/git/newlib-cygwin.git
> >
> >or, for the web view:
> >
> >  https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git
> 
> May I say yeah! And thank you!
> 
> I am sure it will go smoothly. A couple of web pages will need
> updating but that should be it.

There's also some packaging stuff and the snapshot creation scripts
for Cygwin.  But that will come over time.

> Is this basically replacing the git mirror?

I don't know anything about the git mirror.  I'm going to set up
the repo from scratch.  I had a few testruns already and it looks
pretty well, I think.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

       reply	other threads:[~2015-03-05 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150305145541.GA20560@calimero.vinschen.de>
     [not found] ` <F2C22140-82E0-470B-9F87-9DC45503CA9C@oarcorp.com>
2015-03-05 15:59   ` Corinna Vinschen [this message]
     [not found] ` <alpine.DEB.2.10.1503062257590.9654@digraph.polyomino.org.uk>
2015-03-09 10:53   ` Corinna Vinschen
2015-03-05 15:12 Corinna Vinschen
2015-03-10 15:59 ` Jon TURNEY
2015-03-10 19:45   ` Corinna Vinschen

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=20150305155939.GH3213@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=cygwin-developers@cygwin.com \
    --cc=newlib@sourceware.org \
    /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).