[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: shepherd a patch?
From: |
David Nalesnik |
Subject: |
Re: shepherd a patch? |
Date: |
Fri, 15 Nov 2019 08:18:35 -0600 |
James and all,
On Fri, Nov 15, 2019 at 7:31 AM David Nalesnik <address@hidden> wrote:
>
> On Fri, Nov 15, 2019 at 4:31 AM James Lowe <address@hidden> wrote:
> >
> > David et al.
> > >
> > > Am 15.11.19 um 04:10 schrieb David Nalesnik:
> > > > Would someone be willing to shepherd the patch for me?
> >
> > What I would suggest (generally to anyone on this list that ever needs a
> > patch shepherding) is to make sure a tracker exists - @David, as I know you
> > have access to create tickets you can at least do this - and then attach
> > your patch to that and set the tracker to 'started' so that at the very
> > least if (for example) Urs forgets, goes on holiday, has some emergency,
> > that I can at least pick it up/detect it on the countdown and put it up for
> > review myself.
> >
> > I do this all the time for 'drive by' patches.
> >
> > James
> >
>
> Thanks for this explanation. I discovered that my patch had gone to
> Rietveld, only no ticket was created. So the error has to do with the
> issue tracker. Here's hoping that it's possible to do what's left
> manually without too much trouble!
>
> Best,
> David
OK, I _think_ all is well. I created this issue
https://sourceforge.net/p/testlilyissues/issues/5602/
and provided a link to the Rietveld issue.
Best,
David
Re: shepherd a patch?, Jonas Hahnfeld, 2019/11/15