[GSoC] Query regarding microproject

[GSoC] Query regarding microproject

[Umang Parmar]

Hello everyone,

I am interested in micro project "Add configuration options for some commonly used command-line”. So can you point me out to implementations of some current commands which have configuration options and also for which command to add config options.

Thanks,
Umang

Re: [GSoC] Query regarding microproject

[Junio C Hamano]

Umang Parmar <umangjparmar@gmail.com> writes:

> I am interested in micro project "Add configuration options for
> some commonly used command-line”. So can you point me out to
> implementations of some current commands which have configuration
> options and also for which command to add config options.

It is not a homework assignment.

Studying the current system to

 - learn what commands are available (hint: "man git" and read from there)

 - learn what commands and command line options are commonly used (hint:
   learn from your own use of the system)

 - pick one of the commands and its options that interests you

 - find out where that particular command is implemented

are all part of a GSoC microproject.

Thanks for your interest ;-)

Re: [GSoC] Query regarding microproject

[Duy Nguyen]

On Mon, Mar 4, 2019 at 2:43 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Umang Parmar <umangjparmar@gmail.com> writes:
>
> > I am interested in micro project "Add configuration options for
> > some commonly used command-line”. So can you point me out to
> > implementations of some current commands which have configuration
> > options and also for which command to add config options.
>
> It is not a homework assignment.

True. But the last step could be really intimidating at the beginning.
I'll give another hint, do

git log --oneline -- Documentation/config.txt

Look for some interesting changes (e.g. "add something") then "git
show" on that commit, which gives some starting point to focus on.

> Studying the current system to
>
>  - learn what commands are available (hint: "man git" and read from there)
>
>  - learn what commands and command line options are commonly used (hint:
>    learn from your own use of the system)
>
>  - pick one of the commands and its options that interests you
>
>  - find out where that particular command is implemented
>
> are all part of a GSoC microproject.
>
> Thanks for your interest ;-)
-- 
Duy

Re: [GSoC] Query regarding microproject

[Christian Couder]

On Mon, Mar 4, 2019 at 8:54 AM Duy Nguyen <pclouds@gmail.com> wrote:
>
> On Mon, Mar 4, 2019 at 2:43 PM Junio C Hamano <gitster@pobox.com> wrote:
> >
> > Umang Parmar <umangjparmar@gmail.com> writes:
> >
> > > I am interested in micro project "Add configuration options for
> > > some commonly used command-line”. So can you point me out to
> > > implementations of some current commands which have configuration
> > > options and also for which command to add config options.
> >
> > It is not a homework assignment.
>
> True. But the last step could be really intimidating at the beginning.
> I'll give another hint, do
>
> git log --oneline -- Documentation/config.txt
>
> Look for some interesting changes (e.g. "add something") then "git
> show" on that commit, which gives some starting point to focus on.

Yeah, another interesting thing to do to learn more about this could
be to look at previous discussions about this microproject in the
mailing list archive, as I think it has already been discussed last
year.

[GSOC]:query regarding microproject

[Sushma Unnibhavi]

I am planning to do a microproject on using unsigned integral type for collection of bits.If anyone else has not taken it up,I would like to work on it.

Re: [GSOC]:query regarding microproject

[Thomas Gummerer]

Hi,

On 03/05, Sushma Unnibhavi wrote:
> I am planning to do a microproject on using unsigned integral type
> for collection of bits.If anyone else has not taken it up,I would
> like to work on it.

Welcome to the Git project!

We generally do not assign micro-projects to someone in particular.
If nobody has taken it yet feel free to work on it.  Reading through
the page for micro-projects [*1*], there's the following bullet point:

"Select a microproject and check that it has not yet been taken or
discussed by searching the mailing list. Public Inbox is your
friend."

Public Inbox is at https://public-inbox.org/git/, and you should
search through the archive there to see if anyone has started on the
project yet.

*1*: https://git.github.io/SoC-2019-Microprojects/

[GSoC] Query regarding Microproject

[Shanthanu Rai]

Hi, I am a 3rd Computer Science Undergrad at National Institute of
Technology Surathkal, India. I wish to apply to git for GSoC.

I am currently working on the microproject titled "Avoid pipes in git
related commands in test scripts". I found 't/t9116-git-svn-log.sh' to
have some commands wherein output of git is redirected to grep (using
pipe). So shall I go ahead and make the required changes, i.e., redirect
the output of git to a file and grep this file, in the relevant commands?

--
Regards,
Shanthanu S Rai

Re: [GSoC] Query regarding Microproject

[Christian Couder]

Hi,

On Fri, Mar 20, 2020 at 7:39 AM Shanthanu Rai
<shanthanu.s.rai9@gmail.com> wrote:
>
> Hi, I am a 3rd Computer Science Undergrad at National Institute of
> Technology Surathkal, India. I wish to apply to git for GSoC.
>
> I am currently working on the microproject titled "Avoid pipes in git
> related commands in test scripts". I found 't/t9116-git-svn-log.sh' to
> have some commands wherein output of git is redirected to grep (using
> pipe). So shall I go ahead and make the required changes, i.e., redirect
> the output of git to a file and grep this file, in the relevant commands?

Yeah, sure.

In 't/t9116-git-svn-log.sh' it seems to me that some refactoring might
be needed too.

Best,
Christian.

Re: [GSoC] Query regarding Microproject

[Shanthanu]

Hey, I had faced some issues while running tests with the below command:
sh t9116-git-svn-log.sh

I ran the test without making any changes to the file.

To get more verbose output for the reason of failure, I ran:
sh t9116-git-svn-log.sh -v -i -d (-i to figure out why the first test fails)

In the verbose output, I got the below error msg:

Couldn't open a repository: Unable to connect to a repository at URL
'file:///{hidden}/git/t/trash%20directory.t9116-git-svn-log/svnrepo':
Unable to open an ra_local session to URL: Unable to open repository
'file:///{hidden}/git/t/trash%20directory.t9116-git-svn-log/svnrepo':
Expected FS format between '1' and '6'; found format '7' at
{hidden}/git/perl/build/lib/Git/SVN.pm line 310.

I can share the entire verbose output if needed.

On 20/03/20 7:11 pm, Christian Couder wrote:
> Hi,
>
> On Fri, Mar 20, 2020 at 7:39 AM Shanthanu Rai
> <shanthanu.s.rai9@gmail.com> wrote:
>> Hi, I am a 3rd Computer Science Undergrad at National Institute of
>> Technology Surathkal, India. I wish to apply to git for GSoC.
>>
>> I am currently working on the microproject titled "Avoid pipes in git
>> related commands in test scripts". I found 't/t9116-git-svn-log.sh' to
>> have some commands wherein output of git is redirected to grep (using
>> pipe). So shall I go ahead and make the required changes, i.e., redirect
>> the output of git to a file and grep this file, in the relevant commands?
> Yeah, sure.
>
> In 't/t9116-git-svn-log.sh' it seems to me that some refactoring might
> be needed too.
>
> Best,
> Christian.

Re: [GSoC] Query regarding Microproject

[Shanthanu]

I found the solution to my issue. The main error message I had got was

> Expected FS format between '1' and '6'; found format '7' at
> {hidden}/git/perl/build/lib/Git/SVN.pm line 310.
After some online searches, I found out that file system format 7
was 'understood' by subversion 1.9 (Filesystem formats section in
https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/structure).
That's when I realized I was using version 1.9 of subversion.

When I downgraded to subversion 1.8 (which understands file format 6),
all tests passed.

So shouldn't the test file itself have mentioned (say as a comment at 
the top
or in a separate README) that it was expecting subversion 1.8 or lesser on
the system? I am using Ubuntu 18.04 and by default the package manager
installs subversion 1.9.

This issue might also be present in other git-svn test files. (I haven't 
checked
though, not sure how to run just git-svn tests)

Re: [GSoC] Query regarding Microproject

[Christian Couder]

On Sat, Mar 21, 2020 at 10:49 AM Shanthanu <shanthanu.s.rai9@gmail.com> wrote:
>
> I found the solution to my issue. The main error message I had got was
>
> > Expected FS format between '1' and '6'; found format '7' at
> > {hidden}/git/perl/build/lib/Git/SVN.pm line 310.
> After some online searches, I found out that file system format 7
> was 'understood' by subversion 1.9 (Filesystem formats section in
> https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/structure).
> That's when I realized I was using version 1.9 of subversion.
>
> When I downgraded to subversion 1.8 (which understands file format 6),
> all tests passed.

Great!

> So shouldn't the test file itself have mentioned (say as a comment at
> the top
> or in a separate README) that it was expecting subversion 1.8 or lesser on
> the system? I am using Ubuntu 18.04 and by default the package manager
> installs subversion 1.9.

It would be better if the test could be fixed to work with subversion
1.9. Otherwise the test could perhaps check the subversion version and
run only if subversion is version 1.8 or lesser.

> This issue might also be present in other git-svn test files. (I haven't
> checked
> though, not sure how to run just git-svn tests)

Maybe with something like:

$ cd t
$ prove --jobs 8 t91*-svn*.sh

Re: [GSoC] Query regarding Microproject

[Shanthanu]

On 24/03/20 1:01 am, Christian Couder wrote:
>> So shouldn't the test file itself have mentioned (say as a comment at
>> the top
>> or in a separate README) that it was expecting subversion 1.8 or lesser on
>> the system? I am using Ubuntu 18.04 and by default the package manager
>> installs subversion 1.9.
> It would be better if the test could be fixed to work with subversion
> 1.9. Otherwise the test could perhaps check the subversion version and
> run only if subversion is version 1.8 or lesser.

Yeah that makes sense. I will try to look into how the tests can be
fixed to work with svn 1.9.

>> This issue might also be present in other git-svn test files. (I haven't
>> checked
>> though, not sure how to run just git-svn tests)
> Maybe with something like:
>
> $ cd t
> $ prove --jobs 8 t91*-svn*.sh

Thanks. I ran the command and found that all tests (except t9119) fail for
svn 1.9 and pass for 1.8.
t9119 gives the below output for svn 1.8:
skipped: skipping svn-info test (SVN version: 1.8.13 not supported)

't9119-git-svn-info.sh' seems to already have the code to check
the version of subversion. So we could use the same code to check
the correct version in 'lib-git-svn.sh'?

Note that I haven't checked which all subversion versions work for
a given test (only know that svn 1.8 works for all).