{"thread":{"id":"27821","subject":"Shouldn't git-am be able to pass -b to git-mailinfo?","startedAt":"2011-07-15T00:22:06Z","lastAt":"2011-07-15T00:22:06Z","messageCount":1,"participants":["Jan Winkler"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"171391","messageId":"20110715002206.GA19234@louise.pinerecords.com","threadId":"27821","inReplyTo":null,"subject":"Shouldn't git-am be able to pass -b to git-mailinfo?","fromName":"Jan Winkler","fromEmail":"winkler@pinerecords.com","sentAt":"2011-07-15T00:22:06Z","receivedAt":"2011-07-15T00:22:06Z","isPatch":false,"sender":{"key":"winkler@pinerecords.com","avatar":null},"body":"\nHi,\n\nI've been wondering:  git-am can pass -k to git-mailinfo, but not -b.\nIt's thus impossible to preserve a commitmsg starting with a bracketed\ntext.\n\nConsider a commitmsg starting with '[ISSUE-1234] Fix breakage in XY.'\ngit format-patch produces:\n\n    ...\n    Subject: [PATCH] [ISSUE-1234] Fix breakage in XY.\n    ...\n\nApplying this patch using git-am results in commit message starting\neither with\n\n    Fix breakage...\n\nor, using git-am -k, with\n\n    [PATCH] [ISSUE-1234] Fix...\n\nHowever, there is no way to get the original commit message using\ngit-am's interface.  Or am I missing something?\n\nI'd supply a patch straight away, however, I can't think of a long\nversion of -b option to go well with -k/--keep. Any ideas?\n\n-- \nJan Winkler <winkler@pinerecords.com>\n"}]}