public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Roger Sayle <sayle@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 9892454a3d0fc4a741719701f749b8c1e4d47939 Date: Mon, 30 Oct 2023 12:57:54 +0000 (GMT) [thread overview] Message-ID: <20231030125754.586C1385842A@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 9892454a3d0fc4a741719701f749b8c1e4d47939 (commit) from fcd40a093f9e311cf4ff1bf3910f69f261a32e79 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 9892454a3d0fc4a741719701f749b8c1e4d47939 Author: Roger Sayle <roger@nextmovesoftware.com> Date: Mon Oct 30 12:56:56 2023 +0000 Get newlib via git in simtest-howto.html * htdocs/simtest-howto.html: Use git to obtain newlib. diff --git a/htdocs/simtest-howto.html b/htdocs/simtest-howto.html index 2e54476b..d9c027fd 100644 --- a/htdocs/simtest-howto.html +++ b/htdocs/simtest-howto.html @@ -59,9 +59,7 @@ contrib/gcc_update --touch <pre> cd ${TOP} -cvs -d :pserver:anoncvs@sourceware.org:/cvs/src login -# You will be prompted for a password; reply with "anoncvs". -cvs -d :pserver:anoncvs@sourceware.org:/cvs/src co newlib +git clone https://sourceware.org/git/newlib-cygwin.git newlib </pre> <p>Check out the <code>sim</code> and <code>binutils</code> tree:</p> ----------------------------------------------------------------------- Summary of changes: htdocs/simtest-howto.html | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-10-30 12:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231030125754.586C1385842A@sourceware.org \ --to=sayle@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.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: linkBe 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).