From: John Keeping <john@keeping.me.uk>
To: Kirill Berezin <enelar@develop-project.ru>
Cc: git <git@vger.kernel.org>
Subject: Re: git-submodule nested subrepo bug (Segmentation fault)
Date: Mon, 20 May 2013 11:29:26 +0100 [thread overview]
Message-ID: <20130520102925.GM27005@serenity.lan> (raw)
In-Reply-To: <CAAObgf9RNyVOYD00ki347KBqMWoFA3U7-YM3DnLK4yu62SozSQ@mail.gmail.com>
On Mon, May 20, 2013 at 09:32:21AM +0400, Kirill Berezin wrote:
> When you trying to add submodule, that already has submodule, it craches.
> For example you could try: git clone --recursive
> http://github.com/Exsul/al_server
Which version of Git were you using? I was not able to reproduce this
with 1.8.3-rc3.
next prev parent reply other threads:[~2013-05-20 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 5:32 git-submodule nested subrepo bug (Segmentation fault) Kirill Berezin
2013-05-20 10:29 ` John Keeping [this message]
2013-05-22 20:03 ` Kirill Berezin
-- strict thread matches above, loose matches on Subject: below --
2013-05-22 8:08 John Keeping
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=20130520102925.GM27005@serenity.lan \
--to=john@keeping.me.uk \
--cc=enelar@develop-project.ru \
--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).