diff options
author | Owen W. Taylor <otaylor@fishsoup.net> | 2008-11-22 11:36:57 -0500 |
---|---|---|
committer | Owen W. Taylor <otaylor@fishsoup.net> | 2008-11-22 11:36:57 -0500 |
commit | 201bc1b93915b372b7a71756e64e9091df61b0fd (patch) | |
tree | 68c307ec788cd4c54296e1d8ccce3ad5c771a2e6 | |
parent | 2fb7754e13e1524947d8ec7a93a4c0520cda7319 (diff) | |
download | git-bz-201bc1b93915b372b7a71756e64e9091df61b0fd.tar.gz |
Add TODO item: Reconsider initial description for 'git bz file'
-rw-r--r-- | TODO | 19 |
1 files changed, 19 insertions, 0 deletions
@@ -6,6 +6,25 @@ any intention of working on it myself. - Owen +Reconsider initial description for 'git bz file' + + Right now, if you have only a single patch, the initial description is the body + of the bug, and the attachment is done without any other comment. (But + still adds a comment to the bug because every attachment has a comment.) + + I often find I want to have a few sentences about why I'm making the + change different than the body of the commit (or ask someone to look at the + patch or something), so I've been adding extra text and a separator, + which leaves it unclear what the stuff after the separator is. + + Better way to handle it: + + - Start off the initial description empty in the editor + - If the user fills it in, use that as the initial description + and the body of the commit as the comment. + - If the user leaves it empty use the body as the initial description + as currently. + Allow editing comment used for attachments When attaching a revised version of a patch, you really want to be |