From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Konstantin Khomoutov <kostix@bswap.ru>
Cc: git@vger.kernel.org
Subject: Re: Embedding Git Command Line
Date: Sat, 18 May 2024 21:50:00 +0200 (CEST) [thread overview]
Message-ID: <224aff4c-facc-76cd-94c1-8b40f18c0d40@gmx.de> (raw)
In-Reply-To: <20240516181738.g7iw6rfqvjfucoiw@carbon>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Hi,
On Thu, 16 May 2024, Konstantin Khomoutov wrote:
> On Thu, May 16, 2024 at 01:04:35PM +0100, Kevin Gale wrote:
>
> > We are looking to embed version control features into our commercially
> > licensed proprietary product.
> >
> > We haven’t made a decision on which technology yet but Git would be a
> > popular choice.
> [...]
>
> While only tangentially related, I'd point out that if your product is going
> to actually _bundle_ Git, then be prepared that it has quite a hefty set
> of dependencies, so unless you're going to rely on the target OS to provide
> them (which is, as I understand it, a no-go on Windows) you might be required
> to invest considerable effort into that endaevor.
>
> On the other hand, if it's not a shrink-wrap product but rather something
> enterprise-y (kind of software usually installed by a dedicated technician -
> as opposed to being downloaded and click-through installing by a layperson),
> you might just use what Git for Windows ships, I suppose.
Git for Windows offers MinGit (for full details, see
https://github.com/git-for-windows/git/wiki/MinGit), which is a subset of
Git for Windows intended to be bundled by 3rd-party applications. That's
what Visual Studio and GitHub Desktop do.
Ciao,
Johannes
next prev parent reply other threads:[~2024-05-18 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36B52407-B52F-4394-8DF2-F2DF3D3F0504.ref@yahoo.co.uk>
2024-05-16 12:04 ` Embedding Git Command Line Kevin Gale
2024-05-16 15:15 ` brian m. carlson
2024-05-16 18:17 ` Konstantin Khomoutov
2024-05-18 19:50 ` Johannes Schindelin [this message]
2024-05-21 16:00 ` Konstantin Khomoutov
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=224aff4c-facc-76cd-94c1-8b40f18c0d40@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kostix@bswap.ru \
/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).