From 63b315c1c2c28414f4756f2a5401c1e5d38ee104 Mon Sep 17 00:00:00 2001 From: Joey Hess <joey@kitenet.net> Date: Thu, 13 Dec 2007 09:41:43 -0500 Subject: web commit by http://harningt.myopenid.com/ --- doc/tips/integrated_issue_tracking_with_ikiwiki/discussion.mdwn | 2 ++ 1 file changed, 2 insertions(+) (limited to 'doc/tips') 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? -- cgit v1.2.3