From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH htdocs] current: use tabs for gitconfig settings
Date: Tue, 12 Dec 2023 18:18:55 -0500 [thread overview]
Message-ID: <20231212231855.23447-1-vapier@gentoo.org> (raw)
Since git itself prefers tabs to indent, use them here too. This makes
copy & paste "just work", and people/editors that really wants spaces
and never tabs will most likely auto-convert to their preferred indent
level.
Rendering-wise, it's unchanged as HTML/CSS default to 8-space tab stops.
This will allow us to scale the tab size based on the device's size in a
follow up change to make it more readable -- raw spaces wouldn't.
---
current/index.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/current/index.html b/current/index.html
index 66dc5a82b999..db78d46f9075 100644
--- a/current/index.html
+++ b/current/index.html
@@ -82,16 +82,16 @@ For example, you might have:
<pre>
[remote "origin"]
- url = https://sourceware.org/git/binutils-gdb.git
- fetch = +refs/heads/*:refs/remotes/origin/*
+ url = https://sourceware.org/git/binutils-gdb.git
+ fetch = +refs/heads/*:refs/remotes/origin/*
</pre>
And you would edit this to use "ssh:" rather than "https:":
<pre>
[remote "origin"]
- url = ssh://sourceware.org/git/binutils-gdb.git
- fetch = +refs/heads/*:refs/remotes/origin/*
+ url = ssh://sourceware.org/git/binutils-gdb.git
+ fetch = +refs/heads/*:refs/remotes/origin/*
</pre>
Alternatively, to check out a new read-write copy of the repository,
--
2.43.0
next reply other threads:[~2023-12-12 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 23:18 Mike Frysinger [this message]
2023-12-15 15:52 ` Tom Tromey
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=20231212231855.23447-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@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).