Re: Merge ettiquette

2007-08-21 Thread Jacek Laskowski
On 8/20/07, Jacek Laskowski <[EMAIL PROTECTED]> wrote: > I'm going to add it to our documentation so it won't disappear and > wonder where it should end up. "Project Guidelines" [1] seems to be a > goot fit, but I'm not so sure as bylaws != guidelines (?). "Apache > Geronimo Development Process" [

Re: Merge ettiquette

2007-08-20 Thread Jacek Laskowski
On 8/17/07, David Jencks <[EMAIL PROTECTED]> wrote: > I've noticed that sometimes when people merge bug fixes/changes from > one branch to another they don't include the jira number from the > original commit. This makes it exceedingly hard to figure out which > branches something has been fixed i

Re: Merge ettiquette

2007-08-18 Thread Lin Sun
Good point! Thanks :) Lin David Jencks wrote: I've noticed that sometimes when people merge bug fixes/changes from one branch to another they don't include the jira number from the original commit. This makes it exceedingly hard to figure out which branches something has been fixed in from

Merge ettiquette

2007-08-17 Thread David Jencks
I've noticed that sometimes when people merge bug fixes/changes from one branch to another they don't include the jira number from the original commit. This makes it exceedingly hard to figure out which branches something has been fixed in from the jira issue or the commit logs. In the f