From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 5A29C1F727 for ; Mon, 27 Jun 2022 21:21:26 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="PHE0QMQO"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239932AbiF0VVK (ORCPT ); Mon, 27 Jun 2022 17:21:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59230 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239408AbiF0VVJ (ORCPT ); Mon, 27 Jun 2022 17:21:09 -0400 Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0531D18E05 for ; Mon, 27 Jun 2022 14:21:06 -0700 (PDT) Received: by mail-wm1-x336.google.com with SMTP id o19-20020a05600c4fd300b003a0489f414cso2850816wmq.4 for ; Mon, 27 Jun 2022 14:21:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:from:date:subject:fcc:content-transfer-encoding :mime-version:to:cc; bh=i6nJ3ltKQGFUgpnVcrTBfaK/AGtiI0Gb5CcM1yyKHh8=; b=PHE0QMQOKsjwvpazfNyLs8sz8WUqmY1KYj27Pm5ejT8ZENZ6KI2d4F6SW6RhvuT1Yi dGHXvEXKEeV3vx3pGUjLQKp9tsJISPU9acG6gSHfK0SallkgNzLHfdVwHXyMWbZakt0l NClKYmVDnXxe92SGKhqevLsb1AsqSaWhq3TnRFxOS/xwRexur0insxodQkWhyBnd/gGS 9tReCN7eRvSAz8EonMn2Ifhwi+QR5flygW5vE7Uc8Cde1F+4l9QxT1itekNyHE5hNQ/Z UTDh1K6rs1tnIbWIYc/SDJDRwbwWLUt+Ojh+0MH5HssTcfdmfAhCdn+EHG5uz8N/bk5z rD2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:from:date:subject:fcc :content-transfer-encoding:mime-version:to:cc; bh=i6nJ3ltKQGFUgpnVcrTBfaK/AGtiI0Gb5CcM1yyKHh8=; b=FcDVrbAezTB8Nfm1zfYc5dDH7fzYgCTdUhUtWBUC5bm7sjARQBSS3WQn8kclfkwOXy WP54CelS3Robm7e363x9vdLAN0c8j/TALFyFIX44bNnXTxJOoAP0spt9WWhgLYynxyxb 4IraLnyq3dH4Vx9XPvwLWwzjV78IGfsHlyhWtKZz+SayGwxckgWyPTQDM5coG5k2nZGP jJnodu50LimWKLL35Mt1MH0MOsZH9GPlPje7OJHDjhLm7z0iEawTPuiQsomUE8CNuFb1 HZ6J26qCJXF9ZAr8qjhUyDhJzWX+2CXCv3WpE3RFcjop7KxvS0SW5W2GpV4RAPLmcEy+ IDZw== X-Gm-Message-State: AJIora9OqcqPr0gvtpR1bRoTl+ZOHQh8qcMU8NN9fQ/FNa8XpucopeMu 6/6dzTorRbqCrLZXH143Nnp2vhnDFOEdbg== X-Google-Smtp-Source: AGRyM1u3da/0LwU2xaW7TVO0NLC8G/2r3rzKiITVT6G+dS4XJ+iJOwLzpbfPIfUWCAc8+0we+NtkKg== X-Received: by 2002:a05:600c:1906:b0:39c:7f82:3090 with SMTP id j6-20020a05600c190600b0039c7f823090mr22243373wmq.152.1656364863415; Mon, 27 Jun 2022 14:21:03 -0700 (PDT) Received: from [127.0.0.1] ([13.74.141.28]) by smtp.gmail.com with ESMTPSA id m2-20020a7bcb82000000b0039744bd664esm18751550wmi.13.2022.06.27.14.21.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Jun 2022 14:21:02 -0700 (PDT) Message-Id: From: "Derrick Stolee via GitGitGadget" Date: Mon, 27 Jun 2022 21:21:01 +0000 Subject: [PATCH] git-rebase.txt: use back-ticks consistently Fcc: Sent Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 To: git@vger.kernel.org Cc: gitster@pobox.com, me@ttaylorr.com, Johannes.Schindelin@gmx.de, Derrick Stolee , Derrick Stolee Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org From: Derrick Stolee While inspecting the 'git rebase' documentation, I noticed that it is inconsistent with how it uses back-ticks (or other punctuation) for identifying Git commands, command-line arguments, or values for those arguments. Sometimes, an argument (like '--interactive') would appear without any punctuation, causing the argument to not have any special formatting. Other times, arguments or 'git rebase' itself would have single-quotes giving a bold look (in the HTML documentation at least). By consistently using back-ticks, these types of strings appear in a monospace font with special highlighting to appear more clearly as text that exists in a command-line invocation of a Git command. This rather-large diff is the result of scanning git-rebase.txt and adding back-ticks as appropriate. Some are adding back-ticks where there was no punctuation. Others are replacing single quotes. There are also a few minor cleanups in the process, such as one place that did not use tabs for the first paragraph in a bulletted list. Another case still referred to the dashed form, but it was the only use in the file except for the heading and NAME section. Signed-off-by: Derrick Stolee --- git-rebase.txt: use back-ticks consistently While I noticed this inconsistency when looking at git rebase as part of the git rebase --update-refs work, I didn't know the best way to update the document from start to finish. This giant update is probably not the best way to present the change. I can see splitting it up in a few ways, but I wanted to check to first see if that was necessary. If it is, then here are the strategies I considered: 1. Focus on type of update. This would mean a change for adding back-ticks on all --