From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: jnareb@gmail.com, christian.couder@gmail.com,
t.gummerer@gmail.com, git@vger.kernel.org, gitster@pobox.com,
stolee@gmail.com
Subject: Re: [GSoC] Finalising a project
Date: Sat, 1 Feb 2020 22:28:50 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2002012226350.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20200201173841.13760-1-shouryashukla.oo@gmail.com>
Hi Shourya,
On Sat, 1 Feb 2020, Shourya Shukla wrote:
> Following your and Derrick Stolee's discussion[1][2], I wanted to ask
> if it would be okay if I start working on the conversion of 'git
> submodule' from now itself because I inferred that it would take
> quite some time to complete and one season may not be enough for
> the same.
Oh, there is no need to ask for permission in open source to start work on
anything. Just do it. ;-)
> Also, if the need calls, I will keep working on it post GSoC as well as
> it would keep the continuum in place. I understand that it is not an
> easy project and will take quite some time to complete.
Indeed, it will take time. Note that I do not even know whether we will
participate in GSoC this year (your email sounds as if you assumed that
you'd "start your GSoC project early" or something).
> As of now, I am researching how the previous commands were converted
> and check if maybe those ways are feasible to convert 'git-submodule'
> too.
That's a very sensible course of action.
Ciao,
Johannes
>
> I would love to recieve everyone's guidance on this problem and learn
> ways to solve this! :)
>
> Regards,
> Shourya Shukla
>
> [1]: https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001311007590.46@tvgsbejvaqbjf.bet/
> [2]: https://lore.kernel.org/git/39a8c249-f0bc-fb0f-2ed5-5ecceb6d4789@gmail.com/
>
prev parent reply other threads:[~2020-02-01 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 17:38 [GSoC] Finalising a project Shourya Shukla
2020-02-01 21:28 ` Johannes Schindelin [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2002012226350.46@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=shouryashukla.oo@gmail.com \
--cc=stolee@gmail.com \
--cc=t.gummerer@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).