From: eugenio gigante <giganteeugenio2@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: git@vger.kernel.org, karthik nayak <karthik.188@gmail.com>,
ps@pks.im, Christian Couder <christian.couder@gmail.com>
Subject: Re: [RFC][GSoC] Proposal: Refactor git-bisect(1)
Date: Fri, 29 Mar 2024 10:05:35 +0100 [thread overview]
Message-ID: <CAFJh0PRP3kkXpz=PJHT65c7uKpOdkekZAKxWFgxZvHiy33-pbg@mail.gmail.com> (raw)
In-Reply-To: <12a3b951-39b2-4e9b-9e27-cc29a65cc167@gmail.com>
> Thank you for explicitly mentioning this. Apart from this, if there's
> any specific things you need to clarify regarding your availability,
> please do so. For instance, if you have any planned vacation periods
> during which you will be unavailable or some such.
Sure!!
Il giorno gio 28 mar 2024 alle ore 04:23 Kaartic Sivaraam
<kaartic.sivaraam@gmail.com> ha scritto:
>
> Hi Eugenio,
>
> On 22/03/24 15:56, eugenio gigante wrote:>
> > Timeline
> > ------------
> >
> > May 1 - 26:
> > Community bounding Period.
> > Read Documentation.
> > Write Backlog.
> >
> >
> > May 27 - July 8:
> > Implement a new layout for state files.
> > Write tests.
> >
> > July 12 - August 19:
> > Assess and implement backward compatibility.
> >
> > August 19 - Deadline :
> > Write documentation for the project.
> >
> > I can dedicate 3 hours a day during weekdays, and 5 hours during the weekends.
> > > [ ... snip ... ]
> >
> >
> > Biographical information
> > ----------------------------------
> >
> > I’m a former student of Logic and Philosophy who turned to coding
> > after graduating.
> > I have been working as a Developer for NTT Data Italia for a year.
> > I hold a full-time job, but I've seen that it doesn't conflict with
> > the rules of GSoC
> > since I'm an open source beginner. I am fully capable of managing my
> > workload independently,
> > including my working hours. I know it is not ideal, but I can
> > definitely work around
> > my schedule and dedicate time to the project.
> >
>
> Thank you for explicitly mentioning this. Apart from this, if there's
> any specific things you need to clarify regarding your availability,
> please do so. For instance, if you have any planned vacation periods
> during which you will be unavailable or some such.
>
> --
> Sivaraam
prev parent reply other threads:[~2024-03-29 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 10:26 [RFC][GSoC] Proposal: Refactor git-bisect(1) eugenio gigante
2024-03-25 8:27 ` Patrick Steinhardt
2024-03-25 11:00 ` eugenio gigante
2024-03-25 11:24 ` Patrick Steinhardt
2024-03-28 3:23 ` Kaartic Sivaraam
2024-03-29 9:05 ` eugenio gigante [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='CAFJh0PRP3kkXpz=PJHT65c7uKpOdkekZAKxWFgxZvHiy33-pbg@mail.gmail.com' \
--to=giganteeugenio2@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.