git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Chris Packham <judge.packham@gmail.com>,
	John Smith <johsmi9933@inbox.com>, GIT <git@vger.kernel.org>,
	Jens Lehmann <Jens.Lehmann@web.de>
Subject: Re: Why are submodules not automatically handled by default or at least configurable to do so?
Date: Mon, 26 Oct 2015 12:53:28 -0700	[thread overview]
Message-ID: <xmqqoaflh0ef.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kb2kStk0+MqUXREH3g+rqbsXoNiTGj=4SxJ4vOR8TqEcA@mail.gmail.com> (Stefan Beller's message of "Mon, 26 Oct 2015 09:28:11 -0700")

Stefan Beller <sbeller@google.com> writes:

> IIUC at the time submodules were invented, there was need for lots of
> code to be written.
> Each command needed new code to deal with submodules. As there was not
> enough people/time
> to do it properly, the "do nothing" was the safest action which could
> be added fast.

That is quite different from how I remember.  Soon after Linus and I
added the Gitlink in early Apr 20007, an early subproject/gitlink
(thought) experiment was started with help from folks like Steven
Grimm, Jan Hudec, Petr Baudis, Alex Riesen etc.  The first principle
of the design throughout that era was "we admit that we do not know
all the use cases, so let's start small and solid and make sure that
small-and-solid thing can later be enhanced as people discover the
way how they want to work" (you can see me expressing that sentiment
in $gmane/48287, for example).

So it wasn't "not enough people to do it properly" at all.  It was
"we admit that we do not know what is proper, so we defer to actual
users to define what is proper for them".

  reply	other threads:[~2015-10-26 19:53 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 [this message]
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

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqoaflh0ef.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=johsmi9933@inbox.com \
    --cc=judge.packham@gmail.com \
    --cc=sbeller@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).