git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick <oinksocket@letterboxes.org>
To: Davide Fiorentino <davide.fiorentino@gmail.com>
Cc: 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 11:40:15 +0000	[thread overview]
Message-ID: <562F629F.7040206@letterboxes.org> (raw)
In-Reply-To: <EC0D15E1-82B3-4A4C-96DE-8922AB870E2B@gmail.com>

On 27/10/15 10:56, Davide Fiorentino wrote:
> Why not set alias(es) for that?

That counts as a hand-rolled (i.e. ad-hoc) solution.  So not out of the 
question, but I'd rather point my colleagues at something tried and 
tested, rather than simply re-invent wheels, possibly badly.

I'd be interested if there are some out there I could adopt?

But oh yes, there is another difficulty with aliases.  Eclipse users on 
Windows: they don't tend to love it if you tell them to install Cygwin, 
open a shell and type things into it.  The Eclipse experience is 
somewhat fraught already (e.g. EGit running out of memory cloning 
moderate-sized repos, and other UI difficulties). I'd be surprised if 
defining aliases is going to help their user experience.  I'm 
considering suggesting they switch to to IntelliJ, but that's also 
asking quite a lot of people who may be reluctant to relearn their whole 
workflow again, and I'd need to do the research to ensure this doesn't 
just make things more confusing.

Cheers,

N

  reply	other threads:[~2015-10-27 11:40 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 [this message]
2015-10-27 12:16       ` 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=562F629F.7040206@letterboxes.org \
    --to=oinksocket@letterboxes.org \
    --cc=davide.fiorentino@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johsmi9933@inbox.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).