In the future could we avoid those non necessary commit ?
I have started a git convention page here:
http://maven.apache.org/developers/conventions/git.html
See the workflow section.
All fixes/improvements for this doc will be appreciate :-)
2012/11/30 jvan...@apache.org:
Updated Branches:
A question from a git rookie:
If we're applying a proper git patch, then the submitted by row shouldn't
be required in the commit message as git will handle this. Right?
/Anders
On Fri, Nov 30, 2012 at 9:04 AM, Olivier Lamy ol...@apache.org wrote:
In the future could we avoid those non
Patches generated with git-format-patch will retain original author when
applied. This is what we require in m2e for example, it makes much
easier to credit code contributions and generate stats reports.
Patches generated with git-diff (or plain diff, for that matter) do not
have author
I have another suggestion related to commit messages. Generally git commit
messages follow following template:
-
First line contains summary of the change
After one empty line there is more or less free-form text describing the commit
in more detail. This can include:
* lists
* urls
*
