public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. f0a47d383fd6193745f5e2d8dffe5989d652c792 Date: Mon, 20 Jan 2020 19:41:00 -0000 [thread overview] Message-ID: <20200120194124.37043.qmail@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 f0a47d383fd6193745f5e2d8dffe5989d652c792 (commit) from 848266eca465e98e1ad0bfb4dff37a8d0f073898 (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 f0a47d383fd6193745f5e2d8dffe5989d652c792 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon Jan 20 20:40:38 2020 +0100 Refer to git commands (instead of svn) in regression hunting instructions. diff --git a/htdocs/bugs/reghunt.html b/htdocs/bugs/reghunt.html index 48d7d241..c6571be5 100644 --- a/htdocs/bugs/reghunt.html +++ b/htdocs/bugs/reghunt.html @@ -149,14 +149,14 @@ of this document.</p> <h2 id="identify">Identify the patch</h2> -<p>The following <a href="https://gcc.gnu.org/wiki/SvnHelp">SVN -commands</a> are particularly useful to help you identify changes from -one version of a file to another:</p> +<p>The following commands are particularly useful to help you identify +changes from one version of a file to another:</p> <ul> -<li><code>svn diff --help</code></li> -<li><code>svn log --help</code></li> -<li><code>svn annotate --help</code></li> +<li><code>git log --help</code></li> +<li><code>git diff --help</code></li> +<li><code>git show --help</code></li> +<li><code>git annotate --help</code></li> </ul> <p>When you've identified the likely patch out of a set of patches ----------------------------------------------------------------------- Summary of changes: htdocs/bugs/reghunt.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-20 19:41 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=20200120194124.37043.qmail@sourceware.org \ --to=gerald@gcc.gnu.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).