From: Elijah Newren <newren@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] t3424: new rebase testcase documenting a stat-dirty-like failure
Date: Tue, 18 Feb 2020 07:55:59 -0800 [thread overview]
Message-ID: <CABPp-BFz63D9Mm69T9tOQpmQdJuhKbA3_U_Su4dV2XSkZxhTfg@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2002181501240.46@tvgsbejvaqbjf.bet>
On Tue, Feb 18, 2020 at 6:03 AM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
> Hi Elijah,
>
> I am awfully short on time these days, so just a very quick observation:
>
> On Mon, 17 Feb 2020, Elijah Newren via GitGitGadget wrote:
>
> > diff --git a/t/t3424-rebase-across-mode-change.sh b/t/t3424-rebase-across-mode-change.sh
> > new file mode 100755
> > index 00000000000..4d2eb1dd7c6
> > --- /dev/null
> > +++ b/t/t3424-rebase-across-mode-change.sh
> > @@ -0,0 +1,52 @@
> > +#!/bin/sh
> > +
> > +test_description='git rebase across mode change'
> > +
> > +. ./test-lib.sh
> > +
> > +test_expect_success 'setup' '
> > + rm -rf ../stupid &&
> > + git init ../stupid &&
> > + cd ../stupid &&
> > + mkdir DS &&
> > + >DS/whatever &&
> > + git add DS &&
> > + git commit -m base &&
> > +
> > + git branch side1 &&
> > + git branch side2 &&
> > +
> > + git checkout side1 &&
> > + git rm -rf DS &&
> > + ln -s unrelated DS &&
>
> This requires symbolic links. Therefore it won't work on Windows, and will
> at least need the `SYMLINKS` prereq. Maybe there is a way, though, to
> change the test so it does not require a symbolic link here?
Ah, yes, I will fix it up. Thanks.
next prev parent reply other threads:[~2020-02-18 15:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 17:15 [PATCH] t3424: new rebase testcase documenting a stat-dirty-like failure Elijah Newren via GitGitGadget
2020-02-17 19:12 ` Elijah Newren
2020-02-18 15:05 ` Phillip Wood
2020-02-18 15:59 ` Elijah Newren
2020-02-19 11:01 ` Phillip Wood
2020-02-19 16:00 ` Elijah Newren
2020-02-19 16:38 ` Junio C Hamano
2020-02-19 19:33 ` Phillip Wood
2020-02-18 14:03 ` Johannes Schindelin
2020-02-18 15:55 ` Elijah Newren [this message]
2020-02-18 20:55 ` [PATCH v2] " Elijah Newren via GitGitGadget
2020-02-18 21:33 ` Junio C Hamano
2020-02-18 22:01 ` Elijah Newren
2020-02-18 22:15 ` [PATCH v3] t3433: " Elijah Newren via GitGitGadget
2020-02-19 17:04 ` [PATCH v4 0/2] " Elijah Newren via GitGitGadget
2020-02-19 17:04 ` [PATCH v4 1/2] " Elijah Newren via GitGitGadget
2020-02-19 17:04 ` [PATCH v4 2/2] merge-recursive: fix the refresh logic in update_file_flags Elijah Newren via GitGitGadget
2020-02-19 18:40 ` Junio C Hamano
2020-02-19 19:32 ` Elijah Newren
2020-02-19 21:39 ` Junio C Hamano
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=CABPp-BFz63D9Mm69T9tOQpmQdJuhKbA3_U_Su4dV2XSkZxhTfg@mail.gmail.com \
--to=newren@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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).