From 443075fd383c26d267bc872d1ded1560090a5e58 Mon Sep 17 00:00:00 2001 From: Helmut Grohne Date: Mon, 17 Feb 2014 08:45:43 +0100 Subject: comment on descriptive git-annex commit messages --- ..._descriptive_commit_messages_in_git-annex_branch.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'doc') diff --git a/doc/todo/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn b/doc/todo/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn index 3a891fc9b..8b6350a55 100644 --- a/doc/todo/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn +++ b/doc/todo/wishlist:_more_descriptive_commit_messages_in_git-annex_branch.mdwn @@ -37,3 +37,19 @@ in my opinion, the messages should at least contain >> Closing as this is literally impossible to do without making >> git-annex worse. [[done]] --[[Joey]] + +> I'm not sure that the requested feature is that far off. There are two +> aspects, that can be solved relatively easy: +> +> * Recording the name of the remote the commit was issued on. This +> information is simply constant per remote. +> +> * While it is true that there is no 1 on 1 correspondence between commands +> and git-annex commits, it would be entirely possible to add a "message +> journal". Every command issued would start out with writing its +> invocation to the message journal. At the time the journal ends up being +> committed to the git-annex branch, the message journal is used as the +> body of the commit message and truncated. +> +> It is true that these suggestions do not address every aspect of the +> original report, but they would solve about 90%. --[[HelmutGrohne]] -- cgit v1.2.3