Or you could just create one JIRA ticket that you never close and use it in the commit messages for all the minor fixes. It doesn't even have to be in JIRA: you could use eg. WICKET-000 for this.
On Fri, Feb 10, 2012 at 5:25 PM, Johan Compagner <[email protected]>wrote: > That could be tricky, because not all commits are always related to an > issue i think.. > But if the UI gives you the option (in eclipse at least for svn) then it is > easer NOT to forget :) > > > On Fri, Feb 10, 2012 at 17:12, Igor Vaynberg <[email protected] > >wrote: > > > we can write a server hook to make sure the string is present i > > suppose. i am not sure if infra would like that or not... > > > > -igor > > > > On Fri, Feb 10, 2012 at 8:10 AM, Johan Compagner <[email protected]> > > wrote: > > > can we somehow force that? Just like we did with svn that has that > build > > in > > > case:xxx support (in the commit dialog?) > > > > > > But i will place WICKET-XXX then in all my commits from now on > > > > > > > > > On Fri, Feb 10, 2012 at 17:08, Martin Grigorov <[email protected]> > > wrote: > > > > > >> On Fri, Feb 10, 2012 at 6:02 PM, Johan Compagner < > [email protected]> > > >> wrote: > > >> > thx > > >> > so it all depends first on: > > >> > http://studio.plugins.atlassian.com/browse/JGIT-74 > > >> > > > >> > but then if we do the commit, how do we say to git that this is > issue > > >> XXX ? > > >> > So that the plugin knows that that commit is for that issue? > > >> > > > >> > I guess we we need to fill in certain things on commit we should > start > > >> with > > >> > that asap. > > >> > > >> I think adding "WICKET-XXX" is enough. > > >> Currently I use > > >> git log --grep=WICKET-XXX > > >> to find all commits for a specific ticket. Since the history is > > >> locally it is quite fast. > > >> > > >> > > > >> > > > >> > On Fri, Feb 10, 2012 at 16:57, Martin Grigorov < > [email protected]> > > >> wrote: > > >> > > > >> >> https://issues.apache.org/jira/browse/INFRA-4157 > > >> >> > > >> >> On Fri, Feb 10, 2012 at 5:44 PM, Jeremy Thomerson > > >> >> <[email protected]> wrote: > > >> >> > Feel free to email [email protected] to bring the > subject > > up > > >> >> there. > > >> >> > > > >> >> > -- > > >> >> > Jeremy Thomerson > > >> >> > http://wickettraining.com > > >> >> > *Need a CMS for Wicket? Use Brix! http://brixcms.org* > > >> >> > > > >> >> > > > >> >> > On Fri, Feb 10, 2012 at 9:59 AM, Bertrand Guay-Paquet < > > >> >> > [email protected]> wrote: > > >> >> > > > >> >> >> Hi, > > >> >> >> > > >> >> >> I asked the same question on dec 22 and Igor replied : > > >> >> >> > > >> >> >> infra is working on this afaik. > > >> >> >> > > >> >> >> -igor > > >> >> >> > > >> >> >> > > >> >> >> So I guess they haven't finished yet! > > >> >> >> > > >> >> >> Bertrand > > >> >> >> > > >> >> >> > > >> >> >> On 10/02/2012 9:34 AM, Johan Compagner wrote: > > >> >> >> > > >> >> >>> Hi, > > >> >> >>> > > >> >> >>> What "broke" now that we are over to git is the nice link > between > > >> jira > > >> >> >>> issues and the source code > > >> >> >>> so this tab: > > >> >> >>> > > >> >> >>> > > >> >> > > >> > > https://issues.apache.org/**jira/browse/WICKET-1654?page=**com.atlassian > . > > >> >> >>> **jirafisheyeplugin:fisheye-**issuepanel#issue-tabs< > > >> >> > > >> > > > https://issues.apache.org/jira/browse/WICKET-1654?page=com.atlassian.jirafisheyeplugin:fisheye-issuepanel#issue-tabs > > >> >> > > > >> >> >>> > > >> >> >>> (or that subversion tab which ofcourse will not work anymore) > > >> >> >>> > > >> >> >>> is there a solution for that for GIT? > > >> >> >>> So that we can at least backtrack easy what is changed for a > > >> specific > > >> >> >>> issue? > > >> >> >>> > > >> >> >>> > > >> >> > > >> >> > > >> >> > > >> >> -- > > >> >> Martin Grigorov > > >> >> jWeekend > > >> >> Training, Consulting, Development > > >> >> http://jWeekend.com > > >> >> > > >> > > >> > > >> > > >> -- > > >> Martin Grigorov > > >> jWeekend > > >> Training, Consulting, Development > > >> http://jWeekend.com > > >> > > >
