diff options
| author | Joey Hess <joey@kitenet.net> | 2007-12-15 12:29:25 -0500 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2007-12-15 12:29:25 -0500 |
| commit | 5e3a2fb6b102e2a7cb332993b128f17f271ff1fd (patch) | |
| tree | 6f07226bac8600155c469bb259c56f8ab8c3c834 /doc/tips | |
| parent | 290dfde6d452a4c465b94df0276e7d2f7d98a6a4 (diff) | |
| parent | 8d5facac68791c8075834ec3dcb83b7f26ef964a (diff) | |
Merge branch 'master' of ssh://git.kitenet.net/srv/git/ikiwiki.info
Diffstat (limited to 'doc/tips')
| -rw-r--r-- | doc/tips/integrated_issue_tracking_with_ikiwiki/discussion.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/tips/integrated_issue_tracking_with_ikiwiki/discussion.mdwn b/doc/tips/integrated_issue_tracking_with_ikiwiki/discussion.mdwn index afd05f807..8c6a6ecc9 100644 --- a/doc/tips/integrated_issue_tracking_with_ikiwiki/discussion.mdwn +++ b/doc/tips/integrated_issue_tracking_with_ikiwiki/discussion.mdwn @@ -20,6 +20,8 @@ I suppose having a separate branch for public web stuff w/ the following workflo Bug origination point: ... anybody have ideas for this? Create branch at bug origination point and merge into current upstream branches? (I guess this would be where cherry-picking would work best, since the web UI can't do this) > Not sure what you mean. +>> Documentation as to where the bug came from for related branches... +>> Ex: The bug got located in r30, but really came about r10. Desire is to propagate the bug to all everything after r10. Bug naming: any conventions/ideas on how to standardize? Any suggestions on methods of linking commits to bugs without having to modify the bug in each commit? |