On 03/01, Sidhant Sharma wrote:
>
> > If you use PARSE_OPT_HIDDEN, I think you don't need to specify a message.
> > Otherwise, the documentation only has value if it contains more than just
> > the option name, but that is the hard part if you're not familiar with the
> > code. The best place to
> If you use PARSE_OPT_HIDDEN, I think you don't need to specify a message.
> Otherwise, the documentation only has value if it contains more than just the
> option name, but that is the hard part if you're not familiar with the code.
> The best place to find documentation is in the history (gi
Sidhant Sharma writes:
>>> First, I'm not quite sure what to put in the help message for the
>>> options (--quiet, --stateless-rpc, --advertise-refs and
>>> --reject-thin-pack-for-testing).
>> They are currently undocumented. We sometimes have explicitly
>> undocumented options (PARSE_OPT_HIDDEN)
>> First, I'm not quite sure what to put in the help message for the
>> options (--quiet, --stateless-rpc, --advertise-refs and
>> --reject-thin-pack-for-testing).
> They are currently undocumented. We sometimes have explicitly
> undocumented options (PARSE_OPT_HIDDEN) when they are used only
> in
Sidhant Sharma writes:
> Hi,
>> I didn't see anything going on for this one, but you may want to
>> double-check with the ml's archives.
>>
> I checked the archives and there doesn't seem to be any active work on this.
> I made the required changes and ran the test suite. Though all the
> tests p
Hi,
Should I make a patch for this and submit it for discussion on the mailing list?
Regards,
Sidhant Sharma [:tk]
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.
Hi,
> I didn't see anything going on for this one, but you may want to
> double-check with the ml's archives.
>
I checked the archives and there doesn't seem to be any active work on this.
I made the required changes and ran the test suite. Though all the tests pass,
there still are two queries I
Sidhant Sharma writes:
>> There's already work in progress on this project, see the mailing list
>> the last few days.
>>
>
> Okay, in that case, I'd like to try is the one titled "Make upload-pack
> and receive-pack use the parse-options api". In that, I can take up
> the `builtin/receive-pack.c
> There's already work in progress on this project, see the mailing list
> the last few days.
>
Okay, in that case, I'd like to try is the one titled "Make upload-pack
and receive-pack use the parse-options api". In that, I can take up
the `builtin/receive-pack.c` file. Would that be okay?
Than
Sidhant Sharma writes:
> Hi everyone,
>
>
> I'm Sidhant Sharma. I'm looking to participate in GSoC 2016 (and contribute
> to Git in general as well). I read up the pages relating to participation
> in GSoC and selected the microproject "Add configuration options for some
> commonly used com
Hi everyone,
I'm Sidhant Sharma. I'm looking to participate in GSoC 2016 (and contribute
to Git in general as well). I read up the pages relating to participation
in GSoC and selected the microproject "Add configuration options for some
commonly used command-line options". I have some queri
On Mon, Feb 22, 2016 at 4:51 PM, Duy Nguyen wrote:
> OK server is up but very likely misconfigured. If you have experience
> with http server before (I think this is apache), then you can dig in
> t/lib-httpd.sh, study how the server is configured and try to fix it.
Thanks Duy. :) All tests pass
On Mon, Feb 22, 2016 at 5:30 PM, Mehul Jain wrote:
> On Mon, Feb 22, 2016 at 3:50 PM, Duy Nguyen wrote:
>> You may have an http server installed but not suitable for these
>> tests. Try running one test file alone with -v -i, e.g.
>> ./t5539-fetch-http-shallow.sh -v -i and post the output.
>
> He
> On 22 Feb 2016, at 11:21, Lars Schneider wrote:
>
>
>> On 22 Feb 2016, at 11:12, Mehul Jain wrote:
>>
>> On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy
>> wrote:
>>> The simplest way to get back on track for you is probably to start over
>>> with a fresh clone, or (warning: destructive ope
> On 22 Feb 2016, at 11:12, Mehul Jain wrote:
>
> On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy
> wrote:
>> The simplest way to get back on track for you is probably to start over
>> with a fresh clone, or (warning: destructive operations): use git clean
>> to remove untracked files.
>
> Hell
On Mon, Feb 22, 2016 at 3:50 PM, Duy Nguyen wrote:
> You may have an http server installed but not suitable for these
> tests. Try running one test file alone with -v -i, e.g.
> ./t5539-fetch-http-shallow.sh -v -i and post the output.
Here's the output :-
expecting success:
git clone --bare
On Mon, Feb 22, 2016 at 5:12 PM, Mehul Jain wrote:
> On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy
> wrote:
>> The simplest way to get back on track for you is probably to start over
>> with a fresh clone, or (warning: destructive operations): use git clean
>> to remove untracked files.
>
> Hell
On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy
wrote:
> The simplest way to get back on track for you is probably to start over
> with a fresh clone, or (warning: destructive operations): use git clean
> to remove untracked files.
Hello Matthieu,
I followed your advise and cloned a fresh copy of
Please, don't top-post on this list.
Mehul Jain writes:
> Hello,
>
> I faced the following problem when I tested master branch. Here I have
> made no commits to master branch.
Are you sure that 1) you have no uncommitted change and 2) you have
compiled what you have in your tree?
> Is this tes
On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy
wrote:
> Mehul Jain writes:
>
>> Earlier when I was testing the master branch on my pc, I used "make"
>> in \t directory, which lead to failure of test #2, #3 in
>> t5539-fetch-http-shallow.sh .
>> Afterwards I switched to sudo mode and ran the make
Mehul Jain writes:
> Earlier when I was testing the master branch on my pc, I used "make"
> in \t directory, which lead to failure of test #2, #3 in
> t5539-fetch-http-shallow.sh .
> Afterwards I switched to sudo mode and ran the make command again.
Never ever do that. Your git source tree shoul
On Sun, Feb 21, 2016 at 10:25 AM, Matthieu Moy
wrote:
> Please, don't top-post on this list.
I apologize for top-posting on the list.
> Are you sure that 1) you have no uncommitted change and 2) you have
> compiled what you have in your tree?
1) Yes, I have no uncommited change in the branch(ma
On Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller wrote:
> Yes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right
> place as judging from the file name of the tests.
I checked out both of the files and made following observations -
1) As I'm going to add an option for "git
Hello,
I faced the following problem when I tested master branch. Here I have
made no commits to master branch.
*** t5539-fetch-http-shallow.sh ***
ok 1 - setup shallow clone
not ok 2 - clone http repository
#
# git clone --bare --no-local shallow "$HTTPD_DOCUMENT_ROOT_PATH/repo.git" &&
# git clo
On Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller wrote:
> Yes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right
> place as judging from the file name of the tests.
Thanks for specifying the files. I think t/t5520-pull.sh line 258 will
be the best place to write test for th
On Fri, Feb 19, 2016 at 9:39 AM, Mehul Jain wrote:
> On Fri, Feb 19, 2016 at 6:33 PM, Matthieu Moy
> wrote:
>> Hi,
>>
>> This is a double-post. You've posted almost the same message under the
>> title "GSoC 2016". Nothing serious, but attention to details is
>> important if you want to give a goo
On Fri, Feb 19, 2016 at 6:33 PM, Matthieu Moy
wrote:
> Hi,
>
> This is a double-post. You've posted almost the same message under the
> title "GSoC 2016". Nothing serious, but attention to details is
> important if you want to give a good image of yourself.
I'm sorry of this kind of behavior. It
Hi,
This is a double-post. You've posted almost the same message under the
title "GSoC 2016". Nothing serious, but attention to details is
important if you want to give a good image of yourself.
Mehul Jain writes:
> Hello everyone,
>
> I'm Mehul Jain. I'm looking for participating in GSoC 2016.
Hello everyone,
I'm Mehul Jain. I'm looking for participating in GSoC 2016.
I've started work on a Microproject" Teach git pull --rebase the
--no-autostash" option. While looking at Git's source code I have made
following observation: In the pull.c file
1. git_config_get_bool( , ) search in the
29 matches
Mail list logo
