From: Junio C Hamano <gitster@pobox.com>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org, jens.lehmann@web.de, hvoigt@hvoigt.net
Subject: Re: [PATCH v2 0/3] check for unpushed remotes in submodules
Date: Thu, 28 Jul 2011 12:58:27 -0700 [thread overview]
Message-ID: <7v39hqmb30.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1311790250-32454-1-git-send-email-iveqy@iveqy.com> (Fredrik Gustafsson's message of "Wed, 27 Jul 2011 20:10:47 +0200")
Fredrik Gustafsson <iveqy@iveqy.com> writes:
> Regarding the discussion of superprojects with submodules that have no
> remote tracking branches: A push will still be denied.
I have marked one part of the data synchronized across machines as
"private" submodule (which contains my gpg keychains, encrypted password
files, personaly memos, etc.) and push only the outer "shell" superproject
(which has tools that I use everywhere to go to $HOME/bin among other
things) to certain machines without the private parts, and the
superproject is designed to work without a checkout (nor clone) of a
submodule.
With this patch series, it sounds like I cannot use this repository
structure anymore, which is sad.
next prev parent reply other threads:[~2011-07-28 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 18:10 [PATCH v2 0/3] check for unpushed remotes in submodules Fredrik Gustafsson
2011-07-27 18:10 ` [PATCH v2 1/3] test whether push checks " Fredrik Gustafsson
2011-07-27 18:10 ` [PATCH v2 2/3] push: Don't push a repository with unpushed submodules Fredrik Gustafsson
2011-07-27 18:10 ` [PATCH v2 3/3] push: Add the --no-recurse-submodules option Fredrik Gustafsson
2011-07-28 20:05 ` Junio C Hamano
2011-07-28 22:22 ` Jens Lehmann
2011-07-29 20:19 ` Jens Lehmann
2011-08-01 1:16 ` Junio C Hamano
2011-07-28 19:58 ` Junio C Hamano [this message]
2011-07-28 22:14 ` [PATCH v2 0/3] check for unpushed remotes in submodules Jens Lehmann
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=7v39hqmb30.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--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).