From: Heiko Voigt <hvoigt@hvoigt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
git@vger.kernel.org, jens.lehmann@web.de
Subject: Re: [RFC 2/2] Don't push a repository with unpushed submodules
Date: Mon, 4 Jul 2011 22:05:09 +0200 [thread overview]
Message-ID: <20110704200509.GA783@book.hvoigt.net> (raw)
In-Reply-To: <7viprpu1p5.fsf@alter.siamese.dyndns.org>
Hi,
On Tue, Jun 28, 2011 at 01:43:18PM -0700, Junio C Hamano wrote:
> Heiko Voigt <hvoigt@hvoigt.net> writes:
>
> >> What if
> >>
> >> (1) you are binding somebody else's project as your own submodule, you do
> >> not make any local changes (you won't be pushing them out anyway),
> >> and you do not have remote tracking branches in that submodule
> >> project?
> >
> > In this scenario the superproject can not be cloned that way that it
> > would contain the submodule right? I would consider this a rather exotic
> > way to work since pushing means to share your work somehow.
>
> Sorry, I don't follow. Isn't this the classical example of an el-cheapo
> router firmware project (i.e. superproject) binding unmodified Linux
> kernel project as one of its submodules without you having any push
> privilege to Linus's repository, which was one of the original examples
> used in the very initial submodule discussion?
But in such an example the Linux submodule (if used with git submodule)
would have remote tracking branches even though they are not directly
pushable.
Cheers Heiko
next prev parent reply other threads:[~2011-07-04 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 18:29 [RFC 0/2] push checks for unpushed remotes in submodules Fredrik Gustafsson
2011-06-26 18:29 ` [RFC 1/2] test whether " Fredrik Gustafsson
2011-06-26 18:29 ` [RFC 2/2] Don't push a repository with unpushed submodules Fredrik Gustafsson
2011-06-28 18:29 ` Junio C Hamano
2011-06-28 19:30 ` Heiko Voigt
2011-06-28 20:43 ` Junio C Hamano
2011-06-28 21:59 ` Fredrik Gustafsson
2011-06-28 22:24 ` Jens Lehmann
2011-07-04 20:05 ` Heiko Voigt [this message]
2011-06-28 22:06 ` Marc Branchaud
2011-06-28 22:32 ` Jens Lehmann
2011-06-29 17:29 ` Marc Branchaud
2011-06-28 23:02 ` Fredrik Gustafsson
2011-06-29 17:34 ` Marc Branchaud
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=20110704200509.GA783@book.hvoigt.net \
--to=hvoigt@hvoigt.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=iveqy@iveqy.com \
--cc=jens.lehmann@web.de \
/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).