From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Stefan Beller <sbeller@google.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
Eric Sunshine <sunshine@sunshineco.com>,
Jacob Keller <jacob.keller@gmail.com>,
Norio Nomura <norio.nomura@gmail.com>
Subject: Re: [PATCHv3 0/2] Fix relative path issues in recursive submodules.
Date: Wed, 13 Apr 2016 14:03:35 -0700 [thread overview]
Message-ID: <xmqqoa9djk60.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <570E9C46.6080905@ramsayjones.plus.com> (Ramsay Jones's message of "Wed, 13 Apr 2016 20:21:42 +0100")
Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
> Also, I note that t7406-submodule-update.sh test #4 is failing.
> (looks like absolute vs relative paths)
I think that is $gmane/291363
http://thread.gmane.org/gmane.comp.version-control.git/291334/focus=291363
prev parent reply other threads:[~2016-04-13 21:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 0:17 [PATCHv3 0/2] Fix relative path issues in recursive submodules Stefan Beller
2016-04-01 0:17 ` [PATCH 1/2] submodule--helper, module_clone: always operate on absolute paths Stefan Beller
2016-04-01 19:18 ` Junio C Hamano
2016-04-01 19:30 ` Junio C Hamano
2016-04-01 20:09 ` Eric Sunshine
2016-04-01 20:39 ` Junio C Hamano
2016-04-01 0:17 ` [PATCH 2/2] submodule--helper, module_clone: catch fprintf failure Stefan Beller
2016-04-01 14:41 ` [PATCHv3 0/2] Fix relative path issues in recursive submodules Ramsay Jones
2016-04-12 15:58 ` Stefan Beller
2016-04-13 19:21 ` Ramsay Jones
2016-04-13 20:34 ` Stefan Beller
2016-04-13 22:23 ` Junio C Hamano
2016-04-13 22:30 ` Stefan Beller
2016-04-13 22:45 ` Junio C Hamano
2016-04-13 21:03 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqoa9djk60.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=norio.nomura@gmail.com \
--cc=ramsay@ramsayjones.plus.com \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).