+1 for removing redundancy ;) -----Oorspronkelijk bericht----- Van: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] Namens Mason James Verzonden: maandag 1 augustus 2011 02:50 CC: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Patch format i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla an automated bugzilla script could then send that new patch to the patches list this proposed method removes the double-handling of a patch (sending to patches-list and attaching to bugzilla) and would help encourage people to use bugzilla to track their patches, rather than sending the patch to the list, and the patch getting lost a good idea, or not? Mason _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Marcel de Rooy schreef op ma 01-08-2011 om 06:44 [+0000]:
i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla an automated bugzilla script could then send that new patch to the patches list
It's not quite the same, but I use 'git bz' to handle this. So my workflow is along the lines of: *work work code code* git commit git bz apply HEAD (this'll work out the bug number from the commit message) git send-email --to=kpatches HEAD^ It does save hassle on saving files and attaching them to bugs, and so on. Robin.
* Robin Sheat (robin@catalyst.net.nz) wrote:
Marcel de Rooy schreef op ma 01-08-2011 om 06:44 [+0000]:
i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla an automated bugzilla script could then send that new patch to the patches list
It's not quite the same, but I use 'git bz' to handle this. So my workflow is along the lines of:
*work work code code* git commit git bz apply HEAD (this'll work out the bug number from the commit message)
git bz attach maybe?
git send-email --to=kpatches HEAD^
It does save hassle on saving files and attaching them to bugs, and so on.
Robin.
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
participants (3)
-
Chris Cormack -
Marcel de Rooy -
Robin Sheat