[chirp_devel] Editing bugs

[Martin Cooper]

Hi Jim,

Thanks. Yep, I'm familiar with that process, both from reading the wiki
docs and from working on other open source (and commercial) projects that
use it. In this particular case, the bug has been open for a long time, so
I thought I'd mark it as Assigned while I work on it. That said, it's been
open for so long that it's not very likely that someone else has decided to
work on the same thing at the same time now, so it's not really a big deal
if it's not Assigned.

Perhaps this thread will serve as my request for karma.

Thanks,

Martin.
KD6YAM

On Fri, Jun 19, 2020 at 5:53 AM Jim Unroe <rock.unroe at gmail.com> wrote:

> On Fri, Jun 19, 2020 at 12:50 AM Martin Cooper via chirp_devel
> <chirp_devel at intrepid.danplanet.com> wrote:
> >
> > A couple of places in the Developer docs in the wiki talk about
> assigning a bug to yourself so you can work on it. However, I don't seem to
> be able to do that - all I seem to be able to do is add comments. Do I need
> additional karma to be able to edit an issue, so that I can assign it to
> myself while I work on it, and before I submit a patch? If so, how does one
> "apply" for such karma?
> >
> > Thanks,
> >
> > Martin.
>
> If an issue has not already been opened for whatever I am working on,
> I open one. Then I reference the "issue number" (#nnnn) either in the
> subject or body of the commit message. I'm pretty sure that in most
> cases, the reference to the issue number in the commit message is a
> requirement.
>
> It was a long time ago (2012), but I think all I had to do to receive
> the necessary "karma" was to ask for it on the [chirp_devel] mailing
> list.
>
> Jim KC9HI
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20200619/3cfaa41e/attachment-0001.html