git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>, Elijah Newren <newren@gmail.com>
Subject: [PATCH] 2.35.1.txt: clarify the rebase/stash regression
Date: Sat, 29 Jan 2022 02:16:26 +0000	[thread overview]
Message-ID: <pull.1136.git.1643422586267.gitgitgadget@gmail.com> (raw)

From: Elijah Newren <newren@gmail.com>

rebase and stash still worked in v2.35.0 in a secondary worktree so
long as they were invoked from the toplevel directory.  Update the
release note to clarify this.

Signed-off-by: Elijah Newren <newren@gmail.com>
---
    2.35.1.txt: clarify the rebase/stash regression
    
    I haven't seen the release notes go out; I'm hoping this patch is seen
    in time...

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1136%2Fnewren%2Fregression-clarification-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1136/newren/regression-clarification-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1136

 Documentation/RelNotes/2.35.1.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/RelNotes/2.35.1.txt b/Documentation/RelNotes/2.35.1.txt
index 726ba250ef3..0661d8c6e5e 100644
--- a/Documentation/RelNotes/2.35.1.txt
+++ b/Documentation/RelNotes/2.35.1.txt
@@ -2,5 +2,5 @@ Git v2.35.1 Release Notes
 =========================
 
 Git 2.35 shipped with a regression that broke use of "rebase" and
-"stash" in a secondary worktree.  This maintenance release ought to
-fix it.
+"stash" when run from a subdirectory within a secondary worktree.
+This maintenance release fixes it.

base-commit: 5d01301f2b865aa8dba1654d3f447ce9d21db0b5
-- 
gitgitgadget

                 reply	other threads:[~2022-01-29  2:16 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.1136.git.1643422586267.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    /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).