From: Felipe Contreras <felipe.contreras@gmail.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: Git List <git@vger.kernel.org>, Jonathan Nieder <jrn@google.com>,
Jose Lopes <jabolopes@google.com>,
Aleksandr Mikhailov <avmikhailov@google.com>
Subject: Re: Proposal/Discussion: Turning parts of Git into libraries
Date: Thu, 23 Mar 2023 17:37:21 -0600 [thread overview]
Message-ID: <CAMP44s2AMrXCN6f6v-W0sqb++TVfHf7Q1miJE7iZjZOVwFQa0Q@mail.gmail.com> (raw)
In-Reply-To: <CAJoAoZ=Cig_kLocxKGax31sU7Xe4==BGzC__Bg2_pr7krNq6MA@mail.gmail.com>
On Fri, Feb 17, 2023 at 3:45 PM Emily Shaffer <nasamuffin@google.com> wrote:
> As I mentioned in standup this week[1], my colleagues and I at Google
> have become very interested in converting parts of Git into libraries
> usable by external programs. In other words, for some modules which
> already have clear boundaries inside of Git - like config.[ch],
> strbuf.[ch], etc. - we want to remove some implicit dependencies, like
> references to globals, and make explicit other dependencies, like
> references to other modules within Git. Eventually, we'd like both for
> an external program to use Git libraries within its own process, and
> for Git to be given an alternative implementation of a library it uses
> internally (like a plugin at runtime).
This is obviously the way it should have been done from the beginning,
but unfortunately at this point the Git project has too much inertia
and too many vested interests from multi-billion dollar corporations
to change.
I wonder if a single person who isn't paid to work on Git commented on
this thread.
I don't think these kinds of laudable efforts can be achieved within
the Git project.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2023-03-23 23:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 21:12 Proposal/Discussion: Turning parts of Git into libraries Emily Shaffer
2023-02-17 21:21 ` brian m. carlson
2023-02-17 21:38 ` Emily Shaffer
2023-02-17 22:41 ` brian m. carlson
2023-02-17 22:49 ` Emily Shaffer
2023-02-22 19:34 ` Jeff King
2023-02-24 20:31 ` Emily Shaffer
2023-02-24 21:41 ` Jeff King
2023-02-24 22:59 ` Junio C Hamano
2023-02-17 22:04 ` rsbecker
2023-02-17 22:48 ` brian m. carlson
2023-02-17 22:57 ` Junio C Hamano
2023-02-18 1:59 ` demerphq
2023-02-18 10:36 ` Phillip Wood
2023-03-23 23:22 ` Felipe Contreras
2023-03-23 23:30 ` rsbecker
2023-03-23 23:34 ` Felipe Contreras
2023-03-23 23:42 ` rsbecker
2023-03-23 23:55 ` Felipe Contreras
2023-03-24 19:27 ` rsbecker
2023-03-24 21:21 ` Felipe Contreras
2023-03-24 22:06 ` rsbecker
2023-03-24 22:29 ` Felipe Contreras
2023-02-21 21:42 ` Emily Shaffer
2023-02-22 0:22 ` Junio C Hamano
2023-02-18 4:05 ` Elijah Newren
2023-02-21 22:06 ` Emily Shaffer
2023-02-22 8:23 ` Elijah Newren
2023-02-22 19:25 ` Jeff King
2023-02-21 19:09 ` Taylor Blau
2023-02-21 22:27 ` Emily Shaffer
2023-02-22 1:44 ` Victoria Dye
2023-02-25 1:48 ` Jonathan Tan
2023-02-22 14:55 ` Derrick Stolee
2023-02-24 21:06 ` Emily Shaffer
2023-03-23 23:37 ` Felipe Contreras [this message]
2023-03-23 23:44 ` rsbecker
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=CAMP44s2AMrXCN6f6v-W0sqb++TVfHf7Q1miJE7iZjZOVwFQa0Q@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=avmikhailov@google.com \
--cc=git@vger.kernel.org \
--cc=jabolopes@google.com \
--cc=jrn@google.com \
--cc=nasamuffin@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 read-only IMAP folder(s) and NNTP newsgroup(s).