From: Fredrik Gustafsson <iveqy@iveqy.com>
To: iveqy@iveqy.com
Cc: git@vger.kernel.org
Subject: [PATCH v2 0/2] module_list enhancements
Date: Fri, 14 Jun 2013 02:26:01 +0200 [thread overview]
Message-ID: <1371169563-10267-1-git-send-email-iveqy@iveqy.com> (raw)
The first iteration can be found here:
http://thread.gmane.org/gmane.comp.version-control.git/227572/
The errors in the first patch was a faulty test. I also applied Junios solution in the
first patch, it was nicer.
Fredrik Gustafsson (2):
[submodule] handle multibyte characters in name
[submodule] Replace perl-code with sh
git-submodule.sh | 53 ++++++++++++++++++++--------------------------
t/t7400-submodule-basic.sh | 12 +++++++++++
2 files changed, 35 insertions(+), 30 deletions(-)
--
1.8.3.1.381.g2ab719e.dirty
next reply other threads:[~2013-06-14 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 0:26 Fredrik Gustafsson [this message]
2013-06-14 0:26 ` [PATCH v2 1/2] [submodule] handle multibyte characters in name Fredrik Gustafsson
2013-06-14 15:02 ` Junio C Hamano
2013-06-14 0:26 ` [PATCH v2 2/2] [submodule] Replace perl-code with sh Fredrik Gustafsson
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=1371169563-10267-1-git-send-email-iveqy@iveqy.com \
--to=iveqy@iveqy.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).