public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: newlib@sourceware.org, gdb@sourceware.org, gcc@gcc.gnu.org
Subject: Re: Newlib/Cygwin now under GIT
Date: Tue, 10 Mar 2015 16:20:00 -0000	[thread overview]
Message-ID: <54FF19BC.7010308@oarcorp.com> (raw)
In-Reply-To: <20150310153846.GI5732@calimero.vinschen.de>

Thank you for doing this! It cloned for me on the first try.

Any particular reason, the repo is called newlib-cygwin.git
and not the more general newlib.git. Cygwin isn't the
only user of newlib.

--joel

On 3/10/2015 10:38 AM, Corinna Vinschen wrote:
> Hi fellow developers,
>
>
> I'm happy to inform you that the move of Newlib/Cygwin from the src CVS
> repository to the new, combined GIT repository is now final.
>
> Here's how to access the new GIT repository:
>
> Read-only:
>
>   git clone git://sourceware.org/git/newlib-cygwin.git
>
> Read/Write:  
>
>   git clone sourceware.org:/git/newlib-cygwin.git
>
> Web view:
>
>   https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git
>
> Commit messages go to the newlib-cvs and/or cygwin-cvs mailing lists,
> just as before.  Commit messages also create a message to the freenode
> IRC channel #cygwin-developers.
>
> If you find problems, don't hesitate to report them, preferredly  on the
> mailing list
>
>   newlib AT sourceware DOT org
>   
> I'm not a git wizard, rather a wizzard (pardon the discworld reference)
> so help in case of problems is highly appreciated.
>
> Newlib list:  Jeff is on the road for the next couple of days so a
> discussion of this point has to wait a while, but for the time being,
> patches should continue to be accompanied by a ChangeLog entry.
>
>
> Have fun,
> Corinna
>

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985

  reply	other threads:[~2015-03-10 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150305145541.GA20560@calimero.vinschen.de>
2015-03-10 15:38 ` Corinna Vinschen
2015-03-10 16:20   ` Joel Sherrill [this message]
2015-03-10 18:25     ` Corinna Vinschen
2015-03-10 17:03   ` Joseph Myers
2015-03-10 18:19     ` Corinna Vinschen
2015-03-10 18:30       ` DJ Delorie
2015-03-10 20:16       ` 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=54FF19BC.7010308@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --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).