Page History

...

# While fixing a bug you notice something evil that must be fixed.
# First set your current work aside:
$ git stash

# Next go create a new branch and purge the ugliness you just discovered:
$ git create -b my-eyes-are-bleeding master
$ git commit -av

# Now go back to what you were working on:
$ git checkout my-brilliant-idea
$ git stash pop

In order ensure that the commit description contains the correct name and email address for you, it is possible to specify this directly to Git creating or modifying the .gitconfig file in your home directory.

[user]
        name = Random J. Developer
        email = random@developer.example.org

Now all git commits will use this name/email regardless of which repository the changes are being made in.  If you want to specify a different name or email for a specific repository, it is possible to add the same information to the .git/config file in that specific repository.

Formatting Git Commit Comments

...

LU-999 Single line description of the changechange under 64 columns

A more detailed explanation.  This can be as detailed as you'd like.
Please explain both what problem was solved and a high-level
description of how it was solved.  Wrap lines at 72 columns or less.

Signed-off-by: Random J Developer <random@developer.example.org>
Change-Id: Ica9ed1612eab0c4673dee088f8b441d806c64932

...