public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [committed] wwwdocs: gitwrite: Structure a section some more
Date: Thu, 19 Jan 2023 10:33:40 +0100 (CET)	[thread overview]
Message-ID: <20230119093342.36BEB33E96@hamza.pair.com> (raw)

On the way properly mark up a command-line option.

Pushed. (The diff locks quite bigger than it actually is.)

Gerald
---
 htdocs/gitwrite.html | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index e4dadb27..1ffda77a 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -412,12 +412,15 @@ chosen).  You can also push an already existing branch using <code>git
 push users/me me/branch</code>.  Beware that if you have more than one
 personal branch set up locally, simply typing <code>git push
 users/me</code> will potentially push all personal branches based on
-that remote.  Use --dry-run to check that what will be pushed is what
-you intend.  The script <code>contrib/git-add-user-branch.sh</code>
-can be used to create a new personal branch which can be pushed and
-pulled from the <i>users/me</i> remote.</p>
+that remote.</p>
+
+<p>Use <code>--dry-run</code> to check that what will be pushed is what
+you intend.
 
-<p>The script also defines a few useful aliases that can be used with the
+<p>The script <code>contrib/git-add-user-branch.sh</code>
+can be used to create a new personal branch which can be pushed and
+pulled from the <i>users/me</i> remote.
+The script also defines a few useful aliases that can be used with the
 repository:</p>
 
 <ul>
-- 
2.39.0

                 reply	other threads:[~2023-01-19  9:33 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=20230119093342.36BEB33E96@hamza.pair.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@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: 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).