git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org, pclouds@gmail.com, j6t@kdbg.org
Subject: Re: [PATCH 0/2] Port `git submodule init` from shell to C
Date: Tue, 12 Apr 2016 18:41:27 -0700	[thread overview]
Message-ID: <xmqqr3eal1yw.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqh9f6mi9n.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Tue, 12 Apr 2016 18:04:04 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> Stefan Beller <sbeller@google.com> writes:
>
>> This is a resend of origin/sb/submodule-init (and it still applies on 
>> top of submodule-parallel-update)
>
> Resend, or update?  There was some overlap with your recent series
> that fixes "prefix" thing, IIRC.

I've queued one possible resolution on 'pu' and pushed the result
out.  It sends $sm_path to the "helper init", but I think the
implementation of "helper init" now needs to do the equivalent of
"displaypath=$prefix$sm_path" that was done in your prefix fix
series, or something like that.

  reply	other threads:[~2016-04-13  1:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13  0:18 [PATCH 0/2] Port `git submodule init` from shell to C Stefan Beller
2016-04-13  0:18 ` [PATCH 1/2] submodule: port resolve_relative_url " Stefan Beller
2016-04-13  0:18 ` [PATCH 2/2] submodule: port init " Stefan Beller
2016-04-13  1:04 ` [PATCH 0/2] Port `git submodule init` " Junio C Hamano
2016-04-13  1:41   ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-15  0:15 Stefan Beller
2016-02-12 23:39 Stefan Beller
2016-01-15 23:37 Stefan Beller
2016-01-19 23:17 ` Junio C Hamano

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=xmqqr3eal1yw.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=pclouds@gmail.com \
    --cc=sbeller@google.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).