On 9/1/07, mabshoff <[EMAIL PROTECTED]> wrote:
> >
> > In that case, what is the right way to "notify" that a patch has been
> > attached? I guess what I'm saying is: how does the main repository
> > maintainer know where to look for tickets that are probably ready to
> > be closed? Is that manage
On Sep 1, 7:13 pm, David Harvey <[EMAIL PROTECTED]> wrote:
> On Sep 1, 2007, at 1:08 PM, William Stein wrote:
>
>
>
>
>
> > On 9/1/07, David Harvey <[EMAIL PROTECTED]> wrote:
> >> On Sep 1, 2007, at 12:59 PM, Robert Bradshaw wrote:
> Suppose I attach a patch to a ticket, which I believe sol
On Sep 1, 2007, at 1:08 PM, William Stein wrote:
>
> On 9/1/07, David Harvey <[EMAIL PROTECTED]> wrote:
>> On Sep 1, 2007, at 12:59 PM, Robert Bradshaw wrote:
Suppose I attach a patch to a ticket, which I believe solves the
issue. Do I close the ticket at that point myself? Or should t
On 9/1/07, David Harvey <[EMAIL PROTECTED]> wrote:
> On Sep 1, 2007, at 12:59 PM, Robert Bradshaw wrote:
> >> Suppose I attach a patch to a ticket, which I believe solves the
> >> issue. Do I close the ticket at that point myself? Or should the
> >> ticket only be closed by the person who puts the
On Sep 1, 2007, at 12:59 PM, Robert Bradshaw wrote:
>> Suppose I attach a patch to a ticket, which I believe solves the
>> issue. Do I close the ticket at that point myself? Or should the
>> ticket only be closed by the person who puts the patch into the
>> "main" repository?
>>
>> david
>
> I t
On Sep 1, 2007, at 9:57 AM, David Harvey wrote:
>
> Suppose I attach a patch to a ticket, which I believe solves the
> issue. Do I close the ticket at that point myself? Or should the
> ticket only be closed by the person who puts the patch into the
> "main" repository?
>
> david
I think there s
