I've just prepared  a small patch for the Git README.md for submission to 
the project using https://github.com/gitgitgadget/git/pull/1115

The main Git project is in the rc (release candidate phase) so it may not 
be included in the next release.
On Thursday, January 13, 2022 at 6:49:17 PM UTC Philip Oakley wrote:

> The codebase is C89, with just a few C99 items. Make sure that your linter 
> is able to play well with old style 'dumb' (cautiously basic) coding styles.
>
> Its worth reading the https://github.com/git/git/blob/master/README.md 
> for the links to the 
> https://github.com/git/git/blob/master/Documentation/SubmittingPatches 
> and https://github.com/git/git/blob/master/Documentation/CodingGuidelines 
> (which should be mentioned ;-)
>
> Do you have one or two particular examples from the linter?
>
> If you are able to provide translations of error messages there is a 
> companion project seehttps://
> github.com/git/git/blob/master/Documentation/SubmittingPatches#L421-L425 
> and https://github.com/git-l10n/git-po/blob/master/po/README.md
> On Thursday, January 13, 2022 at 4:54:34 PM UTC jaydeep...@gmail.com 
> wrote:
>
>> I want to contribute to git but I have some doubts regarding their 
>> codebase.
>>
>>
>>    1. My ccls linter is picking a lot of syntax errors on the 
>>    codebase(there are no errors/warnings on compilation though). Is the 
>>    codebase based on C99? Because most the errors end in `invalid in C99`
>>    2. Since I am just a beginner, I want to start with something simple. 
>>    Currently the error messages in git for some commands are not that 
>> verbose. 
>>    I want to improve the error messages. Where should I start?
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/c2eda95f-a2a6-4dcd-aa44-d2d5c91482c6n%40googlegroups.com.

Reply via email to