Michael Lutz <michi@xxxxxxxxxxxxxx> wrote: > Sometimes modifying the commit message git-svn creates for a subversion > commit can be useful, for example if the original message contains meta > information not needed in the git clone or information from svn properties > should be stored visibly in the commit message. > > This change adds a hook 'git-svn-msg' analogue to the 'commit-msg' hook. > Additionally to the commit message, the hook is passed the git-svn meta > data by an environment variable. I'm not convinced this is a good feature to support. We already have --no-metadata to remove git-svn-id: lines and I hate that feature because it introduced extra variables for testing/debugging/recovery. Metadata in the commit message is important, if you want to remove it after-the-fact, there's git-filter-branch. When dealing with repositories that have been through several systems (e.g. (CVS|Perforce) -> SVN -> git), it's useful to be able to refer to old mailing list archives that only refer to the original system (since neither SVN nor git existed at the time the email was sent). -- 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