git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Julia Evans <julia@jvns.ca>, Julia Evans <julia@jvns.ca>
Subject: [PATCH] doc: remove stray text in Git data model
Date: Tue, 02 Dec 2025 18:11:24 +0000	[thread overview]
Message-ID: <pull.2014.git.1764699084703.gitgitgadget@gmail.com> (raw)

From: Julia Evans <julia@jvns.ca>

I meant to delete this sentence fragment when rewriting this paragraph,
but accidentally left it in. It's repetitive (since it was meant to be
deleted) and it's causing some formatting issues with the note.

Signed-off-by: Julia Evans <julia@jvns.ca>
---
    doc: Remove stray sentence fragment in Git data model

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-2014%2Fjvns%2Fgitdatamodel-stray-text-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2014/jvns/gitdatamodel-stray-text-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/2014

 Documentation/gitdatamodel.adoc | 2 --
 1 file changed, 2 deletions(-)

diff --git a/Documentation/gitdatamodel.adoc b/Documentation/gitdatamodel.adoc
index 3614f5960e..dcfdff0346 100644
--- a/Documentation/gitdatamodel.adoc
+++ b/Documentation/gitdatamodel.adoc
@@ -235,8 +235,6 @@ there will no longer be a branch that points at the old commit.
 The old commit is recorded in the current branch's <<reflogs,reflog>>,
 so it is still "reachable", but when the reflog entry expires it may
 become unreachable and get deleted.
-
-the old commit will usually not be reachable, so it may be deleted eventually.
 Reachable objects will never be deleted.
 
 [[index]]

base-commit: f0ef5b6d9bcc258e4cbef93839d1b7465d5212b9
-- 
gitgitgadget

                 reply	other threads:[~2025-12-02 18:11 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=pull.2014.git.1764699084703.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=julia@jvns.ca \
    /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 NNTP newsgroup(s).