From: Yaroslav Halchenko <yoh@onerussian.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [wishlist?] make submodule commands robust to having non-submodule Subprojects
Date: Thu, 15 Sep 2016 12:40:35 -0400 [thread overview]
Message-ID: <20160915164035.GL9830@onerussian.com> (raw)
In-Reply-To: <CAGZ79kZLdsKcf0t=dDB24VVe+V=uqQCW_VNQwSJ638m5Keu2nQ@mail.gmail.com>
On Thu, 15 Sep 2016, Stefan Beller wrote:
> > I think it would be more logical to make it a 'warning:' not a 'fatal:' and
> > proceed.
> So maybe we would want to introduce a switch
> `--existing-but-unconfigure-gitlinks=(warn|ignore)`
> as well as
> `git config submodule.existing-but-unconfigured (warn|ignore)`
> for a more permanent solution?
possibly ignorant question: is gitlink === Subproject or a
Subproject is a kinda of a gitlink and there are other gitlinks which
aren't Subprojects? ;)
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
next prev parent reply other threads:[~2016-09-15 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 13:02 [wishlist?] make submodule commands robust to having non-submodule Subprojects Yaroslav Halchenko
2016-09-15 16:05 ` Stefan Beller
2016-09-15 16:40 ` Yaroslav Halchenko [this message]
2016-09-15 17:29 ` Stefan Beller
2016-09-15 18:02 ` Junio C Hamano
2016-09-15 18:12 ` Yaroslav Halchenko
2016-09-15 18:16 ` Stefan Beller
2016-09-15 18:29 ` Junio C Hamano
2016-09-15 18:15 ` Stefan Beller
2016-09-15 18:27 ` Junio C Hamano
2016-09-16 14:11 ` Heiko Voigt
2016-09-16 15:40 ` Jacob Keller
2016-09-16 18:28 ` Junio C Hamano
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=20160915164035.GL9830@onerussian.com \
--to=yoh@onerussian.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.