From: Jens Lehmann <Jens.Lehmann@web.de>
To: shawn wilson <ag4ve.us@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: submodules
Date: Fri, 03 May 2013 21:51:52 +0200 [thread overview]
Message-ID: <51841558.4080004@web.de> (raw)
In-Reply-To: <CAH_OBieziOGOJrr=wFS-DbMOH=qzmECDziT9hQNX5GxKvNhGyw@mail.gmail.com>
Am 03.05.2013 15:45, schrieb shawn wilson:
> So, I actually have another question I wasn't able to get to in this
> example (which has color - sorry - less -F displays it decently)
>
> What is shown here is that trying to add submodules in this repo
> doesn't add the .gitmodules file - I can do it manually, but why isn't
> it adding the file? There's a .git/modules directory populated with
> the right stuff, but no .gitmodules file.
>
> The initial question I was trying to demonstrate was that I've got a
> repo with submodules. When I push branches to most of the modules, a:
> git branch -r shows them for everyone. However, in one repo/module (I
> think it's a repo created with git --bare --shared) no one else can
> see (or pull) the remote branches and if I make a new clone of that
> repo as myself, I can't see them either. However, those branches are
> there and if I check that repo out on its own (not as a submodule of
> the main repo) I and everyone else can see those remote branches.
>
> This is git 1.8.2.1 btw.
Thanks for your report. Unfortunately I'm not able to see much in
your attachment, could you please try to reproduce your problem with
a few shell commands and send these inline?
next prev parent reply other threads:[~2013-05-03 19:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 13:45 submodules shawn wilson
2013-05-03 19:51 ` Jens Lehmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-23 8:38 submodules shawn wilson
2014-01-23 17:20 ` submodules W. Trevor King
2007-08-07 22:37 Submodules Dmitry Kakurin
2007-08-07 22:49 ` Submodules Johannes Schindelin
2007-08-07 23:10 ` Submodules Dmitry Kakurin
2007-08-08 10:27 ` Submodules Sven Verdoolaege
2007-08-07 22:50 ` Submodules Johannes Schindelin
2007-08-07 23:31 ` Submodules Dmitry Kakurin
2007-08-08 0:07 ` Submodules Johannes Schindelin
2007-08-08 10:41 ` Submodules Sven Verdoolaege
2007-08-08 19:33 ` Submodules Junio C Hamano
2007-08-08 19:40 ` Submodules Johannes Schindelin
2007-08-08 19:59 ` Submodules Junio C Hamano
2007-08-08 20:08 ` Submodules Sven Verdoolaege
2007-08-08 22:08 ` Submodules Junio C Hamano
2007-08-08 22:18 ` Submodules Johannes Schindelin
2007-08-08 20:27 ` Submodules Junio C Hamano
2007-08-08 20:47 ` Submodules Andy Parkins
2007-08-08 21:12 ` Submodules Johannes Schindelin
2007-08-09 5:44 ` Submodules Sven Verdoolaege
2007-08-08 19:53 ` Submodules Sven Verdoolaege
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=51841558.4080004@web.de \
--to=jens.lehmann@web.de \
--cc=ag4ve.us@gmail.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 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).