1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
Ideas about additions for git-bz
================================
The presence of an idea here does not necessarily imply that I have
any intention of working on it myself.
- Owen
Allow omitting bug reference when obvious
When there is only one commit, and -u/--add-url has previously been used,
or the commit subject/body contains [Bb]ug #?\d+ you should be able do just:
git bz attach HEAD^
Default to -e/--edit when only one commit
When there is only one commit to attach, we might as well default to
-e/--edit - it's more powerful than the prompt and still allows aborting.
Automatically guess obvious obsoletes
When doing attach -e/--edit, and there is an existing patch who's description
matches the Subject of the attachment, start the Obsoletes line
uncommented?
Handle redirects:
Should follow redirects, both to different URLs and http => https
Better display of errors
The switch to XML-RPC greatly improves errors when filing a new bug,
but other problems (e.g., having stale login cookies when making an
attachment) still just dump HTML pages error pages to the console.
More general patch application
'git bz apply' currently only handles patches formated with
'git format-patch', it should be able to apply general patches
as well. For general patches, you would use information from
bugzilla to prime the author and commit message, but allow
further editing of the commit message.
Make -u/--add-url kinder on the reflog
-u works by resetting, then on each patch, running git cherry-pick
followed by git commit --amend. It would be nice to only have one
(informative) reflog entry for the entire process, or at least avoid
the double commits.
|
