From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Pete Wyckoff <pw@padd.com>,
Luke Diamand <luke@diamand.org>
Subject: [PATCH/RFC v6] git-p4: warn if git authorship won't be retained
Date: Fri, 13 May 2011 20:45:59 +0100 [thread overview]
Message-ID: <1305315960-17818-1-git-send-email-luke@diamand.org> (raw)
Updated version of authorship warning change, with modifications to
test harness as compared to v5 suggested by Junio.
Junio - do you need the same fixes to the test cases I put in earlier
(in 3ea2cfd488ed70e03d8d6f10e601784926db8008)? The redirects have
extra whitespace. If so, how should I best do that?
Thanks!
Luke
Luke Diamand (1):
git-p4: warn if git authorship won't be retained
contrib/fast-import/git-p4 | 33 ++++++++++++++++++++++++++++++-
contrib/fast-import/git-p4.txt | 7 ++++++
t/t9800-git-p4.sh | 41 ++++++++++++++++++++++++++++++++++++++++
3 files changed, 79 insertions(+), 2 deletions(-)
next reply other threads:[~2011-05-13 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 19:45 Luke Diamand [this message]
2011-05-13 19:46 ` [PATCH/RFC v6] git-p4: warn if git authorship won't be retained Luke Diamand
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=1305315960-17818-1-git-send-email-luke@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pw@padd.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.
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).