From: Lars Schneider <redacted>
Map a P4 user to a specific name and email address in Git with the
"git-p4.mapUser" config. The config value must be a string adhering
to the format "p4user -> First Lastname [off-list ref]".
Signed-off-by: Lars Schneider <redacted>
---
Documentation/git-p4.txt | 11 +++++++++
git-p4.py | 9 +++++++
t/t9828-git-p4-map-user.sh | 61 ++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 81 insertions(+)
create mode 100755 t/t9828-git-p4-map-user.sh
@@ -553,6 +553,17 @@ git-p4.keepEmptyCommits:: A changelist that contains only excluded files will be imported as an empty commit if this boolean option is set to true.+git-p4.mapUser::+ Map a P4 user to a name and email address in Git. Use a string+ with the following format to create a mapping:+++-------------+git config --add git-p4.mapUser "p4user -> First Last <mail@address.com>"+-------------+++ A mapping will override any user information from P4. Mappings for+ multiple P4 user can be defined.+ Submit variables ~~~~~~~~~~~~~~~~ git-p4.detectRenames::
@@ -0,0 +1,61 @@+#!/bin/sh++test_description='Clone repositories and map users'++../lib-git-p4.sh++test_expect_success'start p4d''+start_p4d+'++test_expect_success'Create a repo with different users''+client_view"//depot/... //client/..."&&+(+cd"$cli"&&++>author.txt&&+p4addauthor.txt&&+p4submit-d"Add file author\\n"++P4USER=mmax+>max.txt&&+p4addmax.txt&&+p4submit-d"Add file max"++P4USER=mo+>moritz.txt&&+p4addmoritz.txt&&+p4submit-d"Add file moritz"++P4USER=no+>nobody.txt&&+p4addnobody.txt&&+p4submit-d"Add file nobody"+)+'++test_expect_success'Clone repo root path with all history''+client_view"//depot/... //client/..."&&+test_when_finishedcleanup_git&&+(+cd"$git"&&+gitinit.&&+gitconfig--addgit-p4.mapUser"mmax -> Max Mustermann <max@muster.com>"&&+gitconfig--addgit-p4.mapUser"mo -> Moritz Untreu <moritz@untreu.com>"&&+gitp4clone--use-client-spec--destination="$git"//depot@all&&+cat>expect<<-\EOF&&+no<no@client>+MoritzUntreu<moritz@untreu.com>+MaxMustermann<max@muster.com>+Dr.author<author@example.com>+EOF+gitlog--format="%an <%ae>">actual&&+test_cmpexpectactual+)+'++test_expect_success'kill p4d''+kill_p4d+'++test_done
From: Eric Sunshine <hidden> Date: 2016-06-15 23:08:32
On Sun, Feb 28, 2016 at 5:25 AM, [off-list ref] wrote:
Map a P4 user to a specific name and email address in Git with the
"git-p4.mapUser" config. The config value must be a string adhering
to the format "p4user -> First Lastname [off-list ref]".
With the caveat that I'm not a Perforce user, is this arrow "->"
thingy common in the Perforce world, or was it invented with this
patch? If it was invented here, then would it make sense to instead
use a more established format, such as the "authors" mapping file from
git-svn?
p4user = Joe User [off-list ref]
More below...
@@ -553,6 +553,17 @@ git-p4.keepEmptyCommits::+git-p4.mapUser::+ Map a P4 user to a name and email address in Git. Use a string+ with the following format to create a mapping:+++-------------+git config --add git-p4.mapUser "p4user -> First Last <mail@address.com>"+-------------+++ A mapping will override any user information from P4. Mappings for+ multiple P4 user can be defined.
Does this format correctly with Asciidoc, or does the pargraph need to
be left-justified? (I haven't tested it myself.)
From: Lars Schneider <hidden> Date: 2016-06-15 23:08:32
On 28 Feb 2016, at 17:19, Eric Sunshine [off-list ref] wrote:
On Sun, Feb 28, 2016 at 5:25 AM, [off-list ref] wrote:
quoted
Map a P4 user to a specific name and email address in Git with the
"git-p4.mapUser" config. The config value must be a string adhering
to the format "p4user -> First Lastname [off-list ref]".
With the caveat that I'm not a Perforce user, is this arrow "->"
thingy common in the Perforce world, or was it invented with this
patch? If it was invented here, then would it make sense to instead
use a more established format, such as the "authors" mapping file from
git-svn?
p4user = Joe User [off-list ref]
I invented "the arrow" here :-)
I didn't know about the SVN format and I agree it makes sense to reuse
an established format. I will fix this in a reroll.
@@ -553,6 +553,17 @@ git-p4.keepEmptyCommits::+git-p4.mapUser::+ Map a P4 user to a name and email address in Git. Use a string+ with the following format to create a mapping:+++-------------+git config --add git-p4.mapUser "p4user -> First Last <mail@address.com>"+-------------+++ A mapping will override any user information from P4. Mappings for+ multiple P4 user can be defined.
Does this format correctly with Asciidoc, or does the pargraph need to
be left-justified? (I haven't tested it myself.)
I am not exactly sure what you mean. The last paragraph is already left
justified, no? Do you know a good tutorial for Asciidoc? How can I/should
I check these things?
From: Eric Sunshine <hidden> Date: 2016-06-15 23:08:32
On Sun, Feb 28, 2016 at 12:05 PM, Lars Schneider
[off-list ref] wrote:
On 28 Feb 2016, at 17:19, Eric Sunshine [off-list ref] wrote:
quoted
On Sun, Feb 28, 2016 at 5:25 AM, [off-list ref] wrote:
quoted
+git-p4.mapUser::
+ Map a P4 user to a name and email address in Git. Use a string
+ with the following format to create a mapping:
++
+-------------
+git config --add git-p4.mapUser "p4user -> First Last [off-list ref]"
+-------------
++
+ A mapping will override any user information from P4. Mappings for
+ multiple P4 user can be defined.
Does this format correctly with Asciidoc, or does the pargraph need to
be left-justified? (I haven't tested it myself.)
I am not exactly sure what you mean. The last paragraph is already left
justified, no?
Sorry, I meant "does it need to be flush against the left margin (that
is column 0)?" Just picking a file at random, (say
Documentation/blame-options.txt), you see quickly that while the first
paragraph of an entry is indented, subsequent paragraphs belonging to
that entry are not.
Do you know a good tutorial for Asciidoc? How can I/should
I check these things?
I haven't looked at tutorial; I've merely consult the Asciidoc
documentation when needed. Assuming you have the Asciidoc toolchain
installed, the easiest way to check if it formats correctly is to run
"make html" and then look at the built Documentation/git-p4.html in a
browser.
From: Luke Diamand <hidden> Date: 2016-06-15 23:08:32
On 28 February 2016 at 10:25, [off-list ref] wrote:
From: Lars Schneider <redacted>
Map a P4 user to a specific name and email address in Git with the
"git-p4.mapUser" config. The config value must be a string adhering
to the format "p4user -> First Lastname [off-list ref]".
Seems generally fine. I agree with Eric's comments about the "->"
format. One comment below:
Probably better to use more innocuous names. I'm not sure who these
people are, but they might not appreciate being recorded forver in a
git-p4 test script.
Luke
Probably better to use more innocuous names. I'm not sure who these
people are, but they might not appreciate being recorded forver in a
git-p4 test script.
A better name could be
Max Musterman [off-list ref]
Erika Musterman [off-list ref]