From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org, Jens.Lehmann@web.de, gmane@otterhall.com
Subject: Re: [PATCH 0/2] WAS: [PATCH] mv: allow moving nested submodules
Date: Mon, 18 Apr 2016 17:01:45 -0700 [thread overview]
Message-ID: <xmqqwpnu31qu.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1461022884-30819-1-git-send-email-sbeller@google.com> (Stefan Beller's message of "Mon, 18 Apr 2016 16:41:22 -0700")
Stefan Beller <sbeller@google.com> writes:
> A single patch evolves into a series.
Power of code inspection to see bugs that are not reported, perhaps
;-)?
I wonder if we can come up with test cases to cover these potential
issues that are addressed in [1/2]?
Thanks.
next prev parent reply other threads:[~2016-04-19 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 23:41 [PATCH 0/2] WAS: [PATCH] mv: allow moving nested submodules Stefan Beller
2016-04-18 23:41 ` [PATCH 1/2] mv submodule: respect ignore_errors for errors in submodule code Stefan Beller
2016-04-18 23:41 ` [PATCH 2/2] mv: allow moving nested submodules Stefan Beller
2016-04-19 7:13 ` Jacob Keller
2016-04-19 0:01 ` Junio C Hamano [this message]
2016-04-19 16:56 ` [PATCH 0/2] WAS: [PATCH] " Stefan Beller
2016-04-19 18:15 ` 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=xmqqwpnu31qu.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gmane@otterhall.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).