From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
To: git@vger.kernel.org
Cc: Luke Diamand <luke@diamand.org>, Pete Wyckoff <pw@padd.com>
Subject: [PATCH] git-p4: add option to preserve user names
Date: Tue, 19 Apr 2011 19:01:17 +0100 [thread overview]
Message-ID: <1303236078-14011-1-git-send-email-luke@diamand.org> (raw)
Patches from git passed into p4 end up with the committer
being identified as the person who ran git-p4.
With "submit --preserve-user", git-p4 sets P4USER. If the
submitter has sufficient p4 permissions, the p4 equivalent
of the git email committer will be passed into perforce.
Luke Diamand (1):
git-p4: add option to preserve user names
contrib/fast-import/git-p4 | 33 +++++++++++++++++++++++++++++++++
contrib/fast-import/git-p4.txt | 6 ++++++
2 files changed, 39 insertions(+), 0 deletions(-)
next reply other threads:[~2011-04-19 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 18:01 Luke Diamand [this message]
2011-04-19 18:01 ` [PATCH] git-p4: add option to preserve user names Luke Diamand
2011-04-20 0:10 ` Pete Wyckoff
-- strict thread matches above, loose matches on Subject: below --
2011-04-21 19:50 [PATCH/RFC v2] " Luke Diamand
2011-04-21 19:50 ` [PATCH] " Luke Diamand
2011-04-23 11:54 ` Pete Wyckoff
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=1303236078-14011-1-git-send-email-luke@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--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).