From: Eric Sunshine <sunshine@sunshineco.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Duy Nguyen <pclouds@gmail.com>,
Michael Rappazzo <rappazzo@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: [PATCH 0/4] worktree: cleanups & simplification
Date: Fri, 31 Jul 2020 19:32:10 -0400 [thread overview]
Message-ID: <20200731233214.22131-1-sunshine@sunshineco.com> (raw)
The primary change of this series is a response to Junio's
observation[1] that it would be nice if get_main_worktree() didn't
employ special cases for path normalization. I was planning on
investigating the topic eventually anyway but ended up having to
tackle the same sort of manual special case normalization in another
worktree-related topic I'm working on, thus this series fell out
naturally from that other work. Along the way, while re-studying the
worktree code, I came across a few other issues which deserved
attention, but which are not directly related to the other topic I'm
working on, so I bundled all these small changes together here.
Eric Sunshine (4):
worktree: drop pointless strbuf_release()
worktree: drop unused code from get_linked_worktree()
worktree: drop bogus and unnecessary path munging
worktree: retire special-case normalization of main worktree path
worktree.c | 18 +++---------------
1 file changed, 3 insertions(+), 15 deletions(-)
--
2.28.0.203.gce1f2e0ef1
next reply other threads:[~2020-07-31 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 23:32 Eric Sunshine [this message]
2020-07-31 23:32 ` [PATCH 1/4] worktree: drop pointless strbuf_release() Eric Sunshine
2020-07-31 23:32 ` [PATCH 2/4] worktree: drop unused code from get_linked_worktree() Eric Sunshine
2020-07-31 23:32 ` [PATCH 3/4] worktree: drop bogus and unnecessary path munging Eric Sunshine
2020-07-31 23:32 ` [PATCH 4/4] worktree: retire special-case normalization of main worktree path Eric Sunshine
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200731233214.22131-1-sunshine@sunshineco.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=rappazzo@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).