From: Emily Shaffer <emilyshaffer@google.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
albertcui@google.com, "Junio C Hamano" <gitster@pobox.com>,
"Matheus Tavares Bernardino" <matheus.bernardino@usp.br>,
"Shourya Shukla" <periperidip@gmail.com>
Subject: Re: RFC/Discussion - Submodule UX Improvements
Date: Tue, 20 Apr 2021 16:10:49 -0700 [thread overview]
Message-ID: <YH9feTykPhimIA13@google.com> (raw)
In-Reply-To: <CAP8UFD0Ct8NofMdds=w0k1-jjX638L6QJQEJWVxqJ6ZPSoJUjg@mail.gmail.com>
On Sun, Apr 18, 2021 at 07:22:07AM +0200, Christian Couder wrote:
>
> Hi Emily,
>
> On Sat, Apr 17, 2021 at 1:39 AM Emily Shaffer <emilyshaffer@google.com> wrote:
> >
> > Hi folks,
> >
> > As hinted by a couple recent patches, I'm planning on some pretty big submodule
> > work over the next 6 months or so - and Ævar pointed out to me in
> > https://lore.kernel.org/git/87v98p17im.fsf@evledraar.gmail.com that I probably
> > should share some of those plans ahead of time. :) So attached is a lightly
> > modified version of the doc that we've been working on internally at Google,
> > focusing on what we think would be an ideal submodule workflow.
>
> Thanks for sharing this doc! My main concern with this is that we are
> likely to have a GSoC student working soon on finishing to port `git
> submodule` to C code. And I wonder how that would interact with your
> work.
I discussed this a little with Jonathan N and Albert and we think it
probably won't matter too much. If anything, I expect mostly we would
touch the submodule--helper, and not the 'git submodule' builtin. But
just in case - it would be useful if any GSoC student were publishing
their code to a feature branch (on a fork, maybe) so that I could keep
an eye out for possible conflicts that way. Or, at very least, CCing me
and Jonathan N on patches :)
- Emily
next prev parent reply other threads:[~2021-04-20 23:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 23:36 RFC/Discussion - Submodule UX Improvements Emily Shaffer
2021-04-18 5:22 ` Christian Couder
2021-04-20 23:10 ` Emily Shaffer [this message]
2021-04-19 3:20 ` Philippe Blain
2021-04-20 23:03 ` Emily Shaffer
2021-04-20 23:30 ` Junio C Hamano
2021-04-21 2:27 ` Philippe Blain
2021-04-19 12:56 ` Randall S. Becker
2021-04-19 12:56 ` Aaron Schrab
2021-04-20 18:49 ` Emily Shaffer
2021-04-20 19:29 ` Randall S. Becker
2021-04-19 19:14 ` Jacob Keller
2021-04-19 19:28 ` Randall S. Becker
2021-04-20 16:18 ` Jacob Keller
2021-04-20 18:47 ` Emily Shaffer
2021-04-20 19:38 ` Randall S. Becker
2021-04-21 6:57 ` Jacob Keller
2021-04-22 15:32 ` Jacob Keller
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=YH9feTykPhimIA13@google.com \
--to=emilyshaffer@google.com \
--cc=albertcui@google.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=matheus.bernardino@usp.br \
--cc=periperidip@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).