GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing git-scm.com — Git - gitmailmap Documentation
English ▾
Topics ▾
Setup and ConfigGetting and Creating ProjectsBasic SnapshottingBranching and MergingSharing and Updating ProjectsInspection and ComparisonPatchingDebuggingExternal SystemsServer AdminGuides
AdministrationPlumbing Commands
DESCRIPTIONIf the file SYNTAXThe # character begins a comment to the end of line, blank lines are ignored. In the simple form, each line in the file consists of the canonical real name of an author, whitespace, and an email address used in the commit (enclosed by < and >) to map to the name. For example: Proper Name <[email protected]> The more complex forms are: which allows mailmap to replace only the email part of a commit, and: Proper Name <[email protected]> <[email protected]> which allows mailmap to replace both the name and the email of a commit matching the specified commit email address, and: Proper Name <[email protected]> Commit Name <[email protected]> which allows mailmap to replace both the name and the email of a commit matching both the specified commit name and email address. Both E-Mails and names are matched case-insensitively. For example this would also match the Commit Name <[email protected]> above: Proper Name <[email protected]> CoMmIt NaMe <[email protected]> NOTESGit does not follow symbolic links when accessing a EXAMPLESYour history contains commits by two authors, Jane and Joe, whose names appear in the repository under several forms: Joe Developer <[email protected]> Joe R. Developer <[email protected]> Jane Doe <[email protected]> Jane Doe <jane@laptop.(none)> Jane D. <jane@desktop.(none)> Now suppose that Joe wants his middle name initial used, and Jane
prefers her family name fully spelled out. A Joe R. Developer <[email protected]> Jane Doe <[email protected]> Jane Doe <jane@desktop.(none)> Note that there’s no need to map the name for <jane@laptop.(none)> to
only correct the names. However, leaving the obviously broken
<jane@laptop.(none)> and <jane@desktop.(none)> E-Mails as-is is
usually not what you want. A Joe R. Developer <[email protected]> Jane Doe <[email protected]> <jane@laptop.(none)> Jane Doe <[email protected]> <jane@desktop.(none)> Finally, let’s say that Joe and Jane shared an E-Mail address, but not a name, e.g. by having these two commits in the history generated by a bug reporting system. I.e. names appearing in history as: Joe <[email protected]> Jane <[email protected]> A full Joe R. Developer <[email protected]> Jane Doe <[email protected]> <jane@laptop.(none)> Jane Doe <[email protected]> <jane@desktop.(none)> Joe R. Developer <[email protected]> Joe <[email protected]> Jane Doe <[email protected]> Jane <[email protected]> GITPart of the git[1] suite gitmailmap |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |