From: "Carlos Martín Nieto" <cmn@dwim.me>
To: Stefan Beller <sbeller@google.com>,
Pranit Bauva <pranit.bauva@gmail.com>
Cc: Saurabh Jain <saurabhsuniljain@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: Gsoc 16
Date: Thu, 17 Mar 2016 14:00:33 +0100 [thread overview]
Message-ID: <1458219633.2031.7.camel@dwim.me> (raw)
In-Reply-To: <CAGZ79ka9kKm69wdM+KhiTi8im72mMBmxY6VDuNJf6wh1baFWJw@mail.gmail.com>
On Tue, 2016-03-15 at 14:33 -0700, Stefan Beller wrote:
> On Tue, Mar 15, 2016 at 2:23 PM, Pranit Bauva <pranit.bauva@gmail.com
> > wrote:
> >
> > Hey,
> >
> > Open Source projects run because of people who contribute in their
> > free time (mainly). It might not be possible for someone to be
> > active
> > all times Sometimes it may take around 2-3 days. Give it a little
> > more
> > time.
> Adding to that: Not everybody reads the whole list.
> The first mail you sent, was deep down in the thread for rewriting
> rebase --interactive in C instead of shell. The libgit2 maintainer
> (Carlos)
> is highly unlikely to read that as it doesn't affect libgit2.
>
> Posting as a separate thread here increases the chance for him to
> spot this
> message.
>
> Usually you'd cc the people you're addressing as that has highest
> chance that
> the relevant people see your message. (I cc'd Carlos in this message,
> no need
> to resend a third time from you.)
Thanks for the CC. Indeed I generally only look at the git list
sporadically and superficially since most discussions are about the
tool part of git, which doesn't affect the underlying system.
Saurabh, libgit2 development happens on the GitHub repository, so if
you want to contribute, open a pull request there and we'll review the
contributions when we can.
Cheers,
cmn
prev parent reply other threads:[~2016-03-17 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 21:00 Gsoc 16 Saurabh Jain
2016-03-15 21:23 ` Pranit Bauva
2016-03-15 21:33 ` Stefan Beller
2016-03-17 13:00 ` Carlos Martín Nieto [this message]
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=1458219633.2031.7.camel@dwim.me \
--to=cmn@dwim.me \
--cc=git@vger.kernel.org \
--cc=pranit.bauva@gmail.com \
--cc=saurabhsuniljain@gmail.com \
--cc=sbeller@google.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).