From: Junio C Hamano <gitster@pobox.com>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Alangi Derick <alangiderick@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Fixed translation error in config.c file
Date: Thu, 07 May 2015 07:01:50 -0700 [thread overview]
Message-ID: <xmqqlhh0scz5.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACnwZYd-hhS2w33rsQ9xR__gdnCUC8ni2ot=KqViWLNjnWFhjQ@mail.gmail.com> (Thiago Farina's message of "Thu, 7 May 2015 10:39:30 -0300")
Thiago Farina <tfransosi@gmail.com> writes:
> On Thu, May 7, 2015 at 8:36 AM, Alangi Derick <alangiderick@gmail.com> wrote:
>> So what should the Title be? Please i am learning this community so i
>> have to make a lot of mistakes. Pardon me.
> Allow me to say something? Forgive me if it sounds rude, as it might sound.
>
> Git community is highly technical and is about developing and
> improving Git scm tool.
>
> To be honest, I think it is not a place to learn C or how to
> contribute to open source projects.
FWIW, I do not mind explaining things to new people. Teaching new
people is how you grow the community.
I however have finite time budget for that kind of activity, and it
annoys me when I see that an earlier suggestion was apparently not
read, and a question is asked when its answer is already in the
mailbox of who is asking it, e.g.
http://article.gmane.org/gmane.comp.version-control.git/268484
in which I had to repeat what I said in:
http://article.gmane.org/gmane.comp.version-control.git/268335
next prev parent reply other threads:[~2015-05-07 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 20:51 [PATCH] Fixed translation error in config.c file Alangi Derick
2015-05-06 22:30 ` Junio C Hamano
2015-05-07 11:36 ` Alangi Derick
2015-05-07 13:39 ` Thiago Farina
2015-05-07 14:01 ` Junio C Hamano [this message]
2015-05-07 16:28 ` Eric Sunshine
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlhh0scz5.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=alangiderick@gmail.com \
--cc=git@vger.kernel.org \
--cc=tfransosi@gmail.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.
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 NNTP newsgroup(s).