On 02 Mar 2016, at 10:25, Lars Schneider <larsxschneider@xxxxxxxxx> wrote: > >> On 02 Mar 2016, at 06:06, Luke Diamand <luke@xxxxxxxxxxx> wrote: >> >> On 1 March 2016 at 19:15, Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote: >>> On Tue, Mar 1, 2016 at 5:49 AM, <larsxschneider@xxxxxxxxx> 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 <email@xxxxxxxxxxx>". >>>> >>>> Signed-off-by: Lars Schneider <larsxschneider@xxxxxxxxx> >>>> --- >>>> diff --git a/Documentation/git-p4.txt b/Documentation/git-p4.txt >>>> +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@xxxxxxxxxxx>" >>>> +------------- >>>> ++ >>>> +A mapping will override any user information from P4. Mappings for >>>> +multiple P4 user can be defined. >>> >>> Sorry for not paying closer attention the first time, but this needs >>> to be repeated for each P4 user you want to map, right? One can >>> imagine this quickly becoming painful if you have a lot of users to >>> map. Have you considered modeling this after git-svn where you can set >>> an "authors" file (and name the corresponding option --authors-file)? >> >> For most authors it should just use the existing Perforce user >> information. This is (I assume) just for the occasional exception >> where Perforce has the wrong email address. > I agree this is an occasional exception. I use it for users that have been deleted on the Perforce server. > > @Eric: If a user wants to they could create a custom gitconfig and then use the config "include" mechanism to achieve a "authors" file kind of approach. > Is the patch uninteresting for git-p4 as it handles only an occasional exception or did the patch get lost in the noise? :-) Thanks, Lars -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html