[Outreachy]

[Outreachy]

[Sonia John]

git format-patch

[Outreachy]

[N Alain Jr]

Hello.
I'm Alain, an outreachy Intern. I am very excited about the prospect
of contributing to this project for Outreach 2024

[Outreachy]

[Abraham Samuel]

Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and
eager to start making valuable contributions to this project. Thanks

Re: [Outreachy]

[Patrick Steinhardt]

On Tue, Oct 01, 2024 at 10:54:44PM +0100, N Alain Jr wrote:
> Hello.
> I'm Alain, an outreachy Intern. I am very excited about the prospect
> of contributing to this project for Outreach 2024

Hi Alain,

happy to hear that you are interested in contributing to Git as part of
the Outreachy projet. To help us mentors, could you please clarify which
of the two approved projects you are interested in?

Other than that I would strongly recommend reading through [1] and [2],
if you haven't already done so. They should give you some ideas for how
the Outreachy application process is designed to work in the Git project
and lays out the expectation of us mentors.

Let me know in case you have any additional questions!

Patrick

[1]: https://git.github.io/Mentoring-Program-Guide/
[2]: https://git.github.io/General-Microproject-Information/

Re: [Outreachy]

[Phillip Wood]

Hi Abraham

On 02/10/2024 04:04, Abraham Samuel wrote:
> Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and
> eager to start making valuable contributions to this project. Thanks

Happy to hear that you are interested in contributing to Git as part of
the Outreachy projet. To help us mentors, could you please clarify which
of the two approved projects you are interested in?

Other than that I would strongly recommend reading through [1] and [2],
if you haven't already done so. They should give you some ideas for how
the Outreachy application process is designed to work in the Git project
and lays out the expectation of us mentors.

Let me know in case you have any additional questions.

Phillip

[1]: https://git.github.io/Mentoring-Program-Guide/
[2]: https://git.github.io/General-Microproject-Information/

Re: [Outreachy]

[N Alain Jr]

Hi Patrick.
My apologies for not specifying earlier.
I would like to contribute to project [2]...

Finish adding a 'os-version' capability to Git protocol v2

Cheers.

On Wed, Oct 2, 2024 at 1:39 PM Patrick Steinhardt <ps@pks.im> wrote:
>
> On Tue, Oct 01, 2024 at 10:54:44PM +0100, N Alain Jr wrote:
> > Hello.
> > I'm Alain, an outreachy Intern. I am very excited about the prospect
> > of contributing to this project for Outreach 2024
>
> Hi Alain,
>
> happy to hear that you are interested in contributing to Git as part of
> the Outreachy projet. To help us mentors, could you please clarify which
> of the two approved projects you are interested in?
>
> Other than that I would strongly recommend reading through [1] and [2],
> if you haven't already done so. They should give you some ideas for how
> the Outreachy application process is designed to work in the Git project
> and lays out the expectation of us mentors.
>
> Let me know in case you have any additional questions!
>
> Patrick
>
> [1]: https://git.github.io/Mentoring-Program-Guide/
> [2]: https://git.github.io/General-Microproject-Information/

Re: [Outreachy]

[Abraham Samuel]

Hello Philip, thanks for your prompt response. As regards your
request, I want to work on the project description 'Convert unit tests
to use the clar testing framework'.

On Wed, Oct 2, 2024 at 3:04 PM Phillip Wood <phillip.wood123@gmail.com> wrote:
>
> Hi Abraham
>
> On 02/10/2024 04:04, Abraham Samuel wrote:
> > Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and
> > eager to start making valuable contributions to this project. Thanks
>
> Happy to hear that you are interested in contributing to Git as part of
> the Outreachy projet. To help us mentors, could you please clarify which
> of the two approved projects you are interested in?
>
> Other than that I would strongly recommend reading through [1] and [2],
> if you haven't already done so. They should give you some ideas for how
> the Outreachy application process is designed to work in the Git project
> and lays out the expectation of us mentors.
>
> Let me know in case you have any additional questions.
>
> Phillip
>
> [1]: https://git.github.io/Mentoring-Program-Guide/
> [2]: https://git.github.io/General-Microproject-Information/
>

Re: [Outreachy]

[Abraham Samuel]

Hi Philip,
I have read through [1], [2] and other articles relevant to completing
a micro project and contributing to git. After going through the
microproject ideas, I have come up with two possible projects I am
interested in working on.
1. changing the style for 'cd' in the test subshell.
In this following email,
https://lore.kernel.org/git/CAPig+cQpUu2UO-+jWn1nTaDykWnxwuEitzVB7PnW2SS_b7V8Hg@mail.gmail.com/
It explains how to modernise and clean up t7001, and example of which is

* style for `cd` in subshell is:

    (
        cd foo &&
        ...
    ) &&

  not:

    (cd foo &&
        ...

    ) &&.
However, a sample outdated style can be seen in the sample file
t/t5605-clone-local.sh which I would like to work on to change those
instances to the modern accepted code style
Some examples can be seen in the file as follows.
test_expect_success 'local clone without .git suffix' '
git clone -l -s a b &&
(cd b &&
echo false >expect &&
git config --bool core.bare >actual &&
test_cmp expect actual &&
git fetch)
'
test_expect_success 'local clone with .git suffix' '
git clone -l -s a.git c &&
(cd c && git fetch)
'
test_expect_success 'bundle clone with nonexistent HEAD (match default)' '
git clone b2.bundle b2 &&
(cd b2 &&
git fetch &&
git rev-parse --verify refs/heads/main)
'

2. Use test_path_is_* functions in test scripts.
I have found three potential test files in the t/ directory
t5601-clone.sh
test_expect_success 'clone --mirror' '

git clone --mirror src mirror &&
test -f mirror/HEAD &&
test ! -f mirror/file &&
FETCH="$(cd mirror && git config remote.origin.fetch)" &&
test "+refs/*:refs/*" = "$FETCH" &&
MIRROR="$(cd mirror && git config --bool remote.origin.mirror)" &&
test "$MIRROR" = true

'

t7300-clean.sh
test_expect_success 'git clean with skip-worktree .gitignore' '
git update-index --skip-worktree .gitignore &&
rm .gitignore &&
mkdir -p build docs &&
touch a.out src/part3.c docs/manual.txt obj.o build/lib.so &&
git clean &&
test -f Makefile &&
test -f README &&
test -f src/part1.c &&
test -f src/part2.c &&
test ! -f a.out &&
test ! -f src/part3.c &&
test -f docs/manual.txt &&
test -f obj.o &&
test -f build/lib.so &&
git update-index --no-skip-worktree .gitignore &&
git checkout .gitignore
'
t7611-merge-abort.sh
test_expect_success 'fails without MERGE_HEAD (completed merge)' '
git merge clean_branch &&
test ! -f .git/MERGE_HEAD &&
# Merge successfully completed
post_merge_head="$(git rev-parse HEAD)" &&
test_must_fail git merge --abort 2>output &&
test_grep MERGE_HEAD output
'

These tests can be refactored to use the test_path_is_file and
test_path_is_missing functions.

Please kindly let me know the possibility of doing these microprojects.
Thanks
Abraham.
On Thu, Oct 3, 2024 at 3:14 AM Abraham Samuel <sammymore50@gmail.com> wrote:
>
> Hello Philip, thanks for your prompt response. As regards your
> request, I want to work on the project description 'Convert unit tests
> to use the clar testing framework'.
>
> On Wed, Oct 2, 2024 at 3:04 PM Phillip Wood <phillip.wood123@gmail.com> wrote:
> >
> > Hi Abraham
> >
> > On 02/10/2024 04:04, Abraham Samuel wrote:
> > > Hello, I'm Adekunle an Outreachy 2024 intern. I am most excited and
> > > eager to start making valuable contributions to this project. Thanks
> >
> > Happy to hear that you are interested in contributing to Git as part of
> > the Outreachy projet. To help us mentors, could you please clarify which
> > of the two approved projects you are interested in?
> >
> > Other than that I would strongly recommend reading through [1] and [2],
> > if you haven't already done so. They should give you some ideas for how
> > the Outreachy application process is designed to work in the Git project
> > and lays out the expectation of us mentors.
> >
> > Let me know in case you have any additional questions.
> >
> > Phillip
> >
> > [1]: https://git.github.io/Mentoring-Program-Guide/
> > [2]: https://git.github.io/General-Microproject-Information/
> >

Re: [Outreachy]

[Patrick Steinhardt]

Hi Abraham,

On Sun, Oct 06, 2024 at 10:57:26AM +0100, Abraham Samuel wrote:
> Hi Philip,

one note up front: we tend to not top-post on this mailing list. The
reply to an email should either go below the quoted parts, or if you
want to reply to multiple parts of the mail you can provide your answers
inline like I do here.

[snip]
> Please kindly let me know the possibility of doing these microprojects.
> Thanks

All of the examples you picked seem valid. You do not require something
like approval to work on those projects, but it would be nice to check
that there are no concurrent threads on the Git mailing list that handle
the same microprojects. I'm not aware of any though, so please feel free
to pick any one of your proposals and work on it.

Thanks!

Patrick

Re: [Outreachy]

[Abraham Samuel]

On Mon, Oct 7, 2024 at 2:24 PM Abraham Samuel <sammymore50@gmail.com> wrote:
>
>
>
>
> On Mon, 7 Oct 2024, 06:30 Patrick Steinhardt, <ps@pks.im> wrote:
>>
>> Hi Abraham,
>>
>> On Sun, Oct 06, 2024 at 10:57:26AM +0100, Abraham Samuel wrote:
>> > Hi Philip,
>>
>> one note up front: we tend to not top-post on this mailing list. The
>> reply to an email should either go below the quoted parts, or if you
>> want to reply to multiple parts of the mail you can provide your answers
>> inline like I do here.
>
>
> Okay thank you very much Patrick, I apologise for the mistake. I will take that into account
>>
>>
>> [snip]
>> > Please kindly let me know the possibility of doing these microprojects.
>> > Thanks
>>
>> All of the examples you picked seem valid. You do not require something
>> like approval to work on those projects, but it would be nice to check
>> that there are no concurrent threads on the Git mailing list that handle
>> the same microprojects. I'm not aware of any though, so please feel free
>> to pick any one of your proposals and work on it.
>>
>> Thanks!
>>
>> Patrick.

Re: [Outreachy]

[Abraham Samuel]

On Mon, Oct 7, 2024 at 6:30 AM Patrick Steinhardt <ps@pks.im> wrote:
>
> Hi Abraham,
>
> On Sun, Oct 06, 2024 at 10:57:26AM +0100, Abraham Samuel wrote:
> > Hi Philip,
>
> one note up front: we tend to not top-post on this mailing list. The
> reply to an email should either go below the quoted parts, or if you
> want to reply to multiple parts of the mail you can provide your answers
> inline like I do here.
>
> [snip]
> > Please kindly let me know the possibility of doing these microprojects.
> > Thanks
>
> All of the examples you picked seem valid. You do not require something
> like approval to work on those projects, but it would be nice to check
> that there are no concurrent threads on the Git mailing list that handle
> the same microprojects. I'm not aware of any though, so please feel free
> to pick any one of your proposals and work on it.
>
> Thanks!
>
> Patrick

Thank you very much Patrick, I appreciate your time. Please I hope I
am replying the correct way this time.
I have created a pull request on GitGitGadget, please can someone
kindly allow me. Here is the link to the pull request
https://github.com/gitgitgadget/git/pull/1811.
Thank you.

Re: [Outreachy]

[Abraham Samuel]

On Mon, Oct 7, 2024 at 7:48 PM Abraham Samuel <sammymore50@gmail.com> wrote:
>
> On Mon, Oct 7, 2024 at 6:30 AM Patrick Steinhardt <ps@pks.im> wrote:
> >
> > Hi Abraham,
> >
> > On Sun, Oct 06, 2024 at 10:57:26AM +0100, Abraham Samuel wrote:
> > > Hi Philip,
> >
> > one note up front: we tend to not top-post on this mailing list. The
> > reply to an email should either go below the quoted parts, or if you
> > want to reply to multiple parts of the mail you can provide your answers
> > inline like I do here.
> >
> > [snip]
> > > Please kindly let me know the possibility of doing these microprojects.
> > > Thanks
> >
> > All of the examples you picked seem valid. You do not require something
> > like approval to work on those projects, but it would be nice to check
> > that there are no concurrent threads on the Git mailing list that handle
> > the same microprojects. I'm not aware of any though, so please feel free
> > to pick any one of your proposals and work on it.
> >
> > Thanks!
> >
> > Patrick
>
> Thank you very much Patrick, I appreciate your time. Please I hope I
> am replying the correct way this time.
> I have created a pull request on GitGitGadget, please can someone
> kindly allow me. Here is the link to the pull request
> https://github.com/gitgitgadget/git/pull/1811.
> Thank you.

Hi Patrick,
Please I submitted this patch via gitgitgadget from my email
<abrahamadekunle50@gmail.com>
https://lore.kernel.org/git/pull.1811.git.1728328755490.gitgitgadget@gmail.com/.
My github account uses a different email address
<abrahamadekunle50@gmail.com> to the one I applied to outreachy
<sammymore50@gmail.com>. How wanted to draw your attention to the
patch because gitgitgadet did not include the [Outreachy] tag I added
to the title and the patch title does not show the [Outreachy] tag in
the mail list.
Thanks for your time