From: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
To: git@vger.kernel.org
Cc: christian.couder@gmail.com, Junio C Hamano <gitster@pobox.com>,
Taylor Blau <me@ttaylorr.com>,
ZheNing Hu <adlternative@gmail.com>
Subject: Re: [GSoC][PATCH] lib-read-tree-m-3way: modernize a test script (style)
Date: Thu, 27 Jan 2022 18:54:55 +0800 [thread overview]
Message-ID: <CAJyCBOQvOZO9esuP4dZuRmSat8Ug+TJYkjBKqTznM1wq8e85xQ@mail.gmail.com> (raw)
In-Reply-To: <20220123060318.471414-1-shaoxuan.yuan02@gmail.com>
Not sure if this email is overlooked (I understand its content is
lackluster though).
I'm looking forward to participating in this year's GSoC :) And I will
be really appreciated if anyone could possibly reply to it (and my
self-intro).
--
Thanks,
Shaoxuan
On Sun, Jan 23, 2022 at 2:04 PM Shaoxuan Yuan <shaoxuan.yuan02@gmail.com> wrote:
>
> As a microproject, I found another small fix regarding styling to do.
>
> I changed the old style '\' (backslash) to new style "'" (single
> quotes).
>
> And I also fixed some double quotes misuse.
>
> Signed-off-by: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
> ---
> Other than that, I forgot to introduce myself in the last patch and
> here it goes:
>
> I'm Shaoxuan Yuan, currently a sophomore majors in Computer Science and Engineering
> (CSE) @ University of California, Irvine.
>
> I have prior open-source experience in which I was [maintaining|contributing to] the
> Casbin community. My main language is Python, and I'm a C newbie
> because I'm quite interested in contributing to git (since it is in my main daily
> toolkit and it is a charm to wield :-) ).
>
> And for now I'm still taking baby steps trying to crack some test script
> styling issues. After getting more familiar with the git contribution
> process, I will try something bigger (though not THAT big) to get a
> firmer grasp of git.
>
> t/lib-read-tree-m-3way.sh | 154 +++++++++++++++++++-------------------
> 1 file changed, 77 insertions(+), 77 deletions(-)
>
> diff --git a/t/lib-read-tree-m-3way.sh b/t/lib-read-tree-m-3way.sh
> index 168329adbc..e40739b8db 100644
> --- a/t/lib-read-tree-m-3way.sh
> +++ b/t/lib-read-tree-m-3way.sh
> @@ -8,16 +8,16 @@ do
> p=$a$b
> echo This is $p from the original tree. >$p
> echo This is Z/$p from the original tree. >Z/$p
> - test_expect_success \
> - "adding test file $p and Z/$p" \
> - 'git update-index --add $p &&
> - git update-index --add Z/$p'
> + test_expect_success 'adding test file $p and Z/$p' '
> + git update-index --add $p &&
> + git update-index --add Z/$p
> + '
> done
> done
> echo This is SS from the original tree. >SS
> -test_expect_success \
> - 'adding test file SS' \
> - 'git update-index --add SS'
> +test_expect_success 'adding test file SS' '
> + git update-index --add SS
> +'
> cat >TT <<\EOF
> This is a trivial merge sample text.
> Branch A is expected to upcase this word, here.
> @@ -30,12 +30,12 @@ At the very end, here comes another line, that is
> the word, expected to be upcased by Branch B.
> This concludes the trivial merge sample file.
> EOF
> -test_expect_success \
> - 'adding test file TT' \
> - 'git update-index --add TT'
> -test_expect_success \
> - 'prepare initial tree' \
> - 'tree_O=$(git write-tree)'
> +test_expect_success 'adding test file TT' '
> + git update-index --add TT
> +'
> +test_expect_success 'prepare initial tree' '
> + tree_O=$(git write-tree)
> +'
>
> ################################################################
> # Branch A and B makes the changes according to the above matrix.
> @@ -45,48 +45,48 @@ test_expect_success \
>
> to_remove=$(echo D? Z/D?)
> rm -f $to_remove
> -test_expect_success \
> - 'change in branch A (removal)' \
> - 'git update-index --remove $to_remove'
> +test_expect_success 'change in branch A (removal)' '
> + git update-index --remove $to_remove
> +'
>
> for p in M? Z/M?
> do
> echo This is modified $p in the branch A. >$p
> - test_expect_success \
> - 'change in branch A (modification)' \
> - "git update-index $p"
> + test_expect_success 'change in branch A (modification)' '
> + git update-index $p
> + '
> done
>
> for p in AN AA Z/AN Z/AA
> do
> echo This is added $p in the branch A. >$p
> - test_expect_success \
> - 'change in branch A (addition)' \
> - "git update-index --add $p"
> + test_expect_success 'change in branch A (addition)' '
> + git update-index --add $p
> + '
> done
>
> echo This is SS from the modified tree. >SS
> echo This is LL from the modified tree. >LL
> -test_expect_success \
> - 'change in branch A (addition)' \
> - 'git update-index --add LL &&
> - git update-index SS'
> +test_expect_success 'change in branch A (addition)' '
> + git update-index --add LL &&
> + git update-index SS
> +'
> mv TT TT-
> sed -e '/Branch A/s/word/WORD/g' <TT- >TT
> rm -f TT-
> -test_expect_success \
> - 'change in branch A (edit)' \
> - 'git update-index TT'
> +test_expect_success 'change in branch A (edit)' '
> + git update-index TT
> +'
>
> mkdir DF
> echo Branch A makes a file at DF/DF, creating a directory DF. >DF/DF
> -test_expect_success \
> - 'change in branch A (change file to directory)' \
> - 'git update-index --add DF/DF'
> +test_expect_success 'change in branch A (change file to directory)' '
> + git update-index --add DF/DF
> +'
>
> -test_expect_success \
> - 'recording branch A tree' \
> - 'tree_A=$(git write-tree)'
> +test_expect_success 'recording branch A tree' '
> + tree_A=$(git write-tree)
> +'
>
> ################################################################
> # Branch B
> @@ -94,65 +94,65 @@ test_expect_success \
>
> rm -rf [NDMASLT][NDMASLT] Z DF
> mkdir Z
> -test_expect_success \
> - 'reading original tree and checking out' \
> - 'git read-tree $tree_O &&
> - git checkout-index -a'
> +test_expect_success 'reading original tree and checking out' '
> + git read-tree $tree_O &&
> + git checkout-index -a
> +'
>
> to_remove=$(echo ?D Z/?D)
> rm -f $to_remove
> -test_expect_success \
> - 'change in branch B (removal)' \
> - "git update-index --remove $to_remove"
> +test_expect_success 'change in branch B (removal)' '
> + git update-index --remove $to_remove
> +'
>
> for p in ?M Z/?M
> do
> echo This is modified $p in the branch B. >$p
> - test_expect_success \
> - 'change in branch B (modification)' \
> - "git update-index $p"
> + test_expect_success 'change in branch B (modification)' '
> + git update-index $p
> + '
> done
>
> for p in NA AA Z/NA Z/AA
> do
> echo This is added $p in the branch B. >$p
> - test_expect_success \
> - 'change in branch B (addition)' \
> - "git update-index --add $p"
> + test_expect_success 'change in branch B (addition)' '
> + git update-index --add $p
> + '
> done
> echo This is SS from the modified tree. >SS
> echo This is LL from the modified tree. >LL
> -test_expect_success \
> - 'change in branch B (addition and modification)' \
> - 'git update-index --add LL &&
> - git update-index SS'
> +test_expect_success 'change in branch B (addition and modification)' '
> + git update-index --add LL &&
> + git update-index SS
> +'
> mv TT TT-
> sed -e '/Branch B/s/word/WORD/g' <TT- >TT
> rm -f TT-
> -test_expect_success \
> - 'change in branch B (modification)' \
> - 'git update-index TT'
> +test_expect_success 'change in branch B (modification)' '
> + git update-index TT
> +'
>
> echo Branch B makes a file at DF. >DF
> -test_expect_success \
> - 'change in branch B (addition of a file to conflict with directory)' \
> - 'git update-index --add DF'
> -
> -test_expect_success \
> - 'recording branch B tree' \
> - 'tree_B=$(git write-tree)'
> -
> -test_expect_success \
> - 'keep contents of 3 trees for easy access' \
> - 'rm -f .git/index &&
> - git read-tree $tree_O &&
> - mkdir .orig-O &&
> - git checkout-index --prefix=.orig-O/ -f -q -a &&
> - rm -f .git/index &&
> - git read-tree $tree_A &&
> - mkdir .orig-A &&
> - git checkout-index --prefix=.orig-A/ -f -q -a &&
> - rm -f .git/index &&
> - git read-tree $tree_B &&
> - mkdir .orig-B &&
> - git checkout-index --prefix=.orig-B/ -f -q -a'
> +test_expect_success 'change in branch B (addition of a file to conflict with directory)' '
> + git update-index --add DF
> +'
> +
> +test_expect_success 'recording branch B tree' '
> + tree_B=$(git write-tree)
> +'
> +
> +test_expect_success 'keep contents of 3 trees for easy access' '
> + rm -f .git/index &&
> + git read-tree $tree_O &&
> + mkdir .orig-O &&
> + git checkout-index --prefix=.orig-O/ -f -q -a &&
> + rm -f .git/index &&
> + git read-tree $tree_A &&
> + mkdir .orig-A &&
> + git checkout-index --prefix=.orig-A/ -f -q -a &&
> + rm -f .git/index &&
> + git read-tree $tree_B &&
> + mkdir .orig-B &&
> + git checkout-index --prefix=.orig-B/ -f -q -a
> +'
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-01-27 10:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 6:03 [GSoC][PATCH] lib-read-tree-m-3way: modernize a test script (style) Shaoxuan Yuan
2022-01-27 10:54 ` Shaoxuan Yuan [this message]
2022-01-28 8:34 ` Eric Sunshine
2022-01-28 9:51 ` Shaoxuan Yuan
2022-02-05 11:59 ` Eric Sunshine
2022-02-07 13:10 ` Shaoxuan Yuan
2022-01-30 9:43 ` [PATCH v2 0/2] t/lib-read-tree-m-3way: modernize a test script Shaoxuan Yuan
2022-01-30 9:43 ` [PATCH v2 1/2] t/lib-read-tree-m-3way: replace double quotes with single quotes Shaoxuan Yuan
2022-02-01 23:51 ` Junio C Hamano
2022-02-02 4:52 ` Shaoxuan Yuan
2022-01-30 9:43 ` [PATCH v2 2/2] t/lib-read-tree-m-3way: replace spaces with tabs Shaoxuan Yuan
2022-02-01 23:57 ` Junio C Hamano
2022-02-02 4:59 ` Shaoxuan Yuan
2022-02-02 6:42 ` [PATCH v3 1/2] t/lib-read-tree-m-3way: modernize style Shaoxuan Yuan
2022-02-02 6:43 ` [PATCH v3 2/2] t/lib-read-tree-m-3way: indent with tabs Shaoxuan Yuan
2022-02-07 11:54 ` Christian Couder
2022-02-08 1:47 ` Shaoxuan Yuan
2022-02-07 11:41 ` [PATCH v3 1/2] t/lib-read-tree-m-3way: modernize style Christian Couder
2022-02-08 1:43 ` Shaoxuan Yuan
2022-02-08 3:24 ` [PATCH v4 0/2] t/lib-read-tree-m-3way: modernize a test script Shaoxuan Yuan
2022-02-08 3:24 ` [PATCH v4 1/2] t/lib-read-tree-m-3way: modernize style Shaoxuan Yuan
2022-02-08 3:24 ` [PATCH v4 2/2] t/lib-read-tree-m-3way: indent with tabs Shaoxuan Yuan
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=CAJyCBOQvOZO9esuP4dZuRmSat8Ug+TJYkjBKqTznM1wq8e85xQ@mail.gmail.com \
--to=shaoxuan.yuan02@gmail.com \
--cc=adlternative@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).