From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
Cc: Pete Wyckoff <pw@padd.com>, Junio C Hamano <gitster@pobox.com>,
Luke Diamand <luke@diamand.org>
Subject: [PATCH/RFC v3] git-p4: warn if git authorship won't be retained
Date: Tue, 10 May 2011 20:27:32 +0100 [thread overview]
Message-ID: <1305055653-5133-1-git-send-email-luke@diamand.org> (raw)
Updated version of git-p4 authorship warning suggested by Junio,
incorporating fixes for problems in v2 pointed out by Pete Wyckoff.
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 | 46 ++++++++++++++++++++++++++++++++++++++++
3 files changed, 84 insertions(+), 2 deletions(-)
next reply other threads:[~2011-05-10 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 19:27 Luke Diamand [this message]
2011-05-10 19:27 ` [PATCH] git-p4: warn if git authorship won't be retained Luke Diamand
2011-05-10 22:11 ` Luke Diamand
2011-05-10 22:51 ` Junio C Hamano
2011-05-11 7:50 ` Luke Diamand
2011-05-10 23:38 ` 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=1305055653-5133-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).