From: Konstantin Khomoutov <kostix+git@007spb.ru>
To: Nick <oinksocket@letterboxes.org>
Cc: Davide Fiorentino <davide.fiorentino@gmail.com>,
John Smith <johsmi9933@inbox.com>,
git@vger.kernel.org
Subject: Re: Why are submodules not automatically handled by default or at least configurable to do so?
Date: Tue, 27 Oct 2015 15:16:37 +0300 [thread overview]
Message-ID: <20151027151637.d3ed7f0dd8c72c78d373c520@domain007.com> (raw)
In-Reply-To: <562F629F.7040206@letterboxes.org>
On Tue, 27 Oct 2015 11:40:15 +0000
Nick <oinksocket@letterboxes.org> wrote:
> > Why not set alias(es) for that?
[...]
> But oh yes, there is another difficulty with aliases. Eclipse users
> on Windows:
[...]
Not to counter your actual argument, but AFAIK EGit uses JGit which is
a Java implementation which does not call out to the "real" Git binary.
This basically means that if something gets implemented in the stock
Git, this won't affect JGit and EGit untill their respective
maintainers implement the same feature.
> they don't tend to love it if you tell them to install
> Cygwin, open a shell and type things into it.
On Windows, you typically want them to use Git for Windows, not
Cygwin. Various GUI front-ends to Git working on Windows (such as Git
Extentions and TortoiseGit) rely on GfW to work as well.
prev parent reply other threads:[~2015-10-27 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 23:10 Why are submodules not automatically handled by default or at least configurable to do so? John Smith
2015-10-26 0:56 ` Chris Packham
2015-10-26 16:28 ` Stefan Beller
2015-10-26 19:53 ` Junio C Hamano
2015-10-26 4:48 ` Nazri Ramliy
2015-10-26 16:56 ` Jens Lehmann
2015-10-28 7:36 ` Nazri Ramliy
2015-10-27 10:50 ` Nick
2015-10-27 10:56 ` Davide Fiorentino
2015-10-27 11:40 ` Nick
2015-10-27 12:16 ` Konstantin Khomoutov [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=20151027151637.d3ed7f0dd8c72c78d373c520@domain007.com \
--to=kostix+git@007spb.ru \
--cc=davide.fiorentino@gmail.com \
--cc=git@vger.kernel.org \
--cc=johsmi9933@inbox.com \
--cc=oinksocket@letterboxes.org \
/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).