From: larsxschneider@gmail.com
To: git@vger.kernel.org
Cc: luke@diamand.org, Lars Schneider <larsxschneider@gmail.com>
Subject: [PATCH v7] git-p4: add config git-p4.pathEncoding
Date: Mon, 14 Sep 2015 19:10:39 +0200 [thread overview]
Message-ID: <1442250640-93838-1-git-send-email-larsxschneider@gmail.com> (raw)
From: Lars Schneider <larsxschneider@gmail.com>
diff to v6:
* Always print the encoded path in verbose mode.
v6 is already on next (a9e383). This patch must be applied on next.
Is this the right way to handle this situation?
Thanks,
Lars
Lars Schneider (1):
git-p4: improve path encoding verbose output
git-p4.py | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
--
2.5.1
next reply other threads:[~2015-09-14 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 17:10 larsxschneider [this message]
2015-09-14 17:10 ` [PATCH v7] git-p4: improve path encoding verbose output larsxschneider
2015-09-14 18:40 ` Junio C Hamano
2015-09-15 15:55 ` Lars Schneider
2015-09-15 7:31 ` Luke Diamand
2015-09-15 7:36 ` Luke Diamand
2015-09-15 15:59 ` Lars Schneider
2015-09-14 18:25 ` [PATCH v7] git-p4: add config git-p4.pathEncoding 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442250640-93838-1-git-send-email-larsxschneider@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=luke@diamand.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).