diff options
author | Joey Hess <joeyh@joeyh.name> | 2017-02-07 12:48:12 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2017-02-07 12:48:12 -0400 |
commit | adb4360505772172db1882ee3f0e7f685aa8ef4b (patch) | |
tree | 2306660612d3756f67324a44d065ac3a46fabe69 /doc | |
parent | ec4d0e737736f69113e8c428fd07b85a313e2f17 (diff) |
comment
Diffstat (limited to 'doc')
-rw-r--r-- | doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit/comment_1_c8836a164c8c1efedd5467233237bfd0._comment | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit/comment_1_c8836a164c8c1efedd5467233237bfd0._comment b/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit/comment_1_c8836a164c8c1efedd5467233237bfd0._comment new file mode 100644 index 000000000..ba8526a34 --- /dev/null +++ b/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit/comment_1_c8836a164c8c1efedd5467233237bfd0._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-02-07T16:39:59Z" + content=""" +Such an env var could easily be supported. + +It's desirable to mostly keep the mantainace of the git-annex branch +out of the user's view, because it's a complication that should not +need to worry about. + +Keeping it in an env var does avoid complicating the discoverable +interface with some parameter to specifiy the commit message. Another +way would be to make the commit message configurable in git config. +Then it could be overridden with -c. Seems like the user of this +feature is likely going to also use annex.alwayscommit=false sometimes +in order to construct git-annex branch commits that bundle up several +changes. + +Anyway, I'm curious what kind of use cases make using custom commit +messages for the git-annex branch makes sense. I doubt that typical git +workflows with cherry-picking patches, patch review, etc, work with that +branch. +"""]] |