On 21/05/12 15:16, Outback Dingo wrote: > On Mon, May 21, 2012 at 8:52 AM, John Crispin <j...@phrozen.org> wrote: >> On 21/05/12 14:41, Outback Dingo wrote: >>> On Sat, May 19, 2012 at 4:20 PM, Philip Prindeville >>> <philipp_s...@redfish-solutions.com> wrote: >>>> We talked about how this could be improved... we're more than a year down >>>> the road, and I'm not seeing much difference. >>>> >>>> Maybe we need to talk about this more? >>>> >>>> Or try harder? >>> >>> One thing Ive noticed is its quite difficult to know whos done what as >>> far as patches / ports looking at patchwork >>> seems few of us actually have access to take / mark / close any >>> specific patch, once they hit they list. Even Ive tried >>> to in patchwork but i see no place to assign a ticket to myself or >>> take ownership and close it when completed, or let >>> someone know im working on it. >>> >> >> >> if you create an accoutn in patchwork you will be able to edit your own >> patches... patchwork matches the email addr for this afaik >> >> John > > I have a patchwork account, Im loggen in right now and i see no way to assign > or > delegate patches to myself that have been submitted to the list. like > i just completed > http://patchwork.openwrt.org/patch/2162/ > but dont see any place in the gui to assign it to me, or close it > even........... maybe permissions?? >
as i said, those patches sent to the list by you are editable by you. It wont be possible for you to close tickets that enter patchwork that are not sent by you as you do not have developer access _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
