From: Felipe Contreras <felipe.contreras@gmail.com>
To: Philippe Blain <levraiphilippeblain@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
git@vger.kernel.org
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Luke Shumaker" <lukeshu@lukeshu.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH v2 0/2] extra: new concept of extra components
Date: Mon, 12 Jul 2021 12:55:14 -0500 [thread overview]
Message-ID: <60ec8202213a1_a231f20891@natae.notmuch> (raw)
In-Reply-To: <c530dedb-8cad-2a73-5b56-a32173046382@gmail.com>
Philippe Blain wrote:
> Le 2021-07-10 à 19:46, Felipe Contreras a écrit :
> > We might want to move more components from contrib to extra once their
> > tests are being run reliably.
> >
> > And we might move some components from the core which aren't really part
> > of the core to extra, like gitk, git-gui, git-p4, and git-svn.
> >
> > For now only contrib/completion and contrib/workdir are graduated to the
> > new area.
>
> ... when I read this I went "what is this workdir thing, it must date from before
> 'git worktree' was added". And combing through the history, it does. The latest
> commit to the script is e32afab7b0 (git-new-workdir: don't fail if the target
> directory is empty, 2014-11-26), which describes as v2.3.0-rc0~60^2. And
> 'git worktree' was shipped in Git 2.5, 2015-07-27.
>
> Looking at the tests, I see two uses of 'git-new-workdir':
> $ git grep -p 'new-workdir'
> t1021-rerere-in-workdir.sh=28=test_expect_success SYMLINKS 'rerere in workdir' '
> t1021-rerere-in-workdir.sh:30:56: "$SHELL_PATH" "$TEST_DIRECTORY/../contrib/workdir/git-new-workdir" . work &&
> t1021-rerere-in-workdir.sh:41:50:# For the purpose of helping contrib/workdir/git-new-workdir users, we do not
> t1021-rerere-in-workdir.sh=44=test_expect_failure SYMLINKS 'rerere in workdir (relative)' '
> t1021-rerere-in-workdir.sh:46:56: "$SHELL_PATH" "$TEST_DIRECTORY/../contrib/workdir/git-new-workdir" . krow &&
> t3000-ls-files-others.sh=75=test_expect_success SYMLINKS 'ls-files --others with symlinked submodule' '
> t3000-ls-files-others.sh:87:57: "$SHELL_PATH" "$TEST_DIRECTORY/../contrib/workdir/git-new-workdir" ../sub sub &&
>
> So they are not really testing this script per se, more like testing rerere and ls-files
> in a worktree created by 'git-new-workdir'. I do not think this enough justification
> to include 'git new-workdir' in 'extra/', since 'git worktree add' does the same thing
> and is a builtin command. Even if its "BUGS" section in the doc says it's "in general [...]
> still experimental", an experimental builtin is better than a 'contrib' script, no ?
I agree.
However, that points out to another problem: the tests should not be using `git new-workdir`.
I'm fine with dropping the last patch from the series.
--
Felipe Contreras
next prev parent reply other threads:[~2021-07-12 17:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 23:46 [PATCH v2 0/2] extra: new concept of extra components Felipe Contreras
2021-07-10 23:46 ` [PATCH v2 1/2] completion: graduate out of contrib Felipe Contreras
2021-07-10 23:46 ` [PATCH v2 2/2] git-new-workdir: " Felipe Contreras
2021-07-12 17:43 ` [PATCH v2 0/2] extra: new concept of extra components Philippe Blain
2021-07-12 17:55 ` Felipe Contreras [this message]
2021-07-13 0:17 ` Junio C Hamano
2021-07-13 1:19 ` Felipe Contreras
2021-07-14 20:23 ` [PATCH v3 0/1] " Felipe Contreras
2021-07-14 20:23 ` [PATCH v3 1/1] completion: graduate out of contrib Felipe Contreras
2021-07-14 23:03 ` Ævar Arnfjörð Bjarmason
2021-07-14 23:17 ` Ævar Arnfjörð Bjarmason
2021-07-15 19:12 ` Felipe Contreras
2021-07-16 6:36 ` Ævar Arnfjörð Bjarmason
2021-07-16 20:14 ` Felipe Contreras
2021-07-15 18:59 ` Felipe Contreras
2021-07-16 20:14 ` [PATCH v4 0/1] extra: new concept of extra components Felipe Contreras
2021-07-16 20:14 ` [PATCH v4 1/1] completion: graduate out of contrib Felipe Contreras
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=60ec8202213a1_a231f20891@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=levraiphilippeblain@gmail.com \
--cc=lukeshu@lukeshu.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).