Will Newton <[EMAIL PROTECTED]> writes:
> On Sunday 07 Apr 2002 3:20 pm, David Starner wrote:
>
> > Why? Considering how close to the release we are, and how easy it is,
> > why not do it now? It certainly won't interfer with the maintainer
> > closing them.
>
> OK, done. I just don't want to st
On Sunday 07 Apr 2002 3:20 pm, David Starner wrote:
> Why? Considering how close to the release we are, and how easy it is,
> why not do it now? It certainly won't interfer with the maintainer
> closing them.
OK, done. I just don't want to step on anyone's toes.
--
To UNSUBSCRIBE, email to [EM
On Sun, Apr 07, 2002 at 03:04:43PM +0100, Will Newton wrote:
> On Sunday 07 Apr 2002 2:44 pm, Josip Rodin wrote:
>
> > Since you're not a maintainer, you shouldn't close them. However, you can
> > tag them "fixed", by sending 'tag fixed' commands to [EMAIL PROTECTED]
>
> OK, if Craig hasn't
On Sunday 07 Apr 2002 2:44 pm, Josip Rodin wrote:
> Since you're not a maintainer, you shouldn't close them. However, you can
> tag them "fixed", by sending 'tag fixed' commands to [EMAIL PROTECTED]
OK, if Craig hasn't done it by the end of today I will do that.
--
To UNSUBSCRIBE, email t
On Sun, Apr 07, 2002 at 11:34:13PM +1000, Martijn van Oosterhout wrote:
> Read up on the BTS docs, but the common ways are:
>
> Email to [EMAIL PROTECTED] with body: "close 140049"
No! Don't fucking do that!
Geez, how many times does one have to repeat that.
--
2. That which causes joy or
On Sun, Apr 07, 2002 at 02:26:30PM +0100, Will Newton wrote:
> I have still not had any response to this. Can anyone tell me the correct
> procedure for getting these bugs closed?
Since you're not a maintainer, you shouldn't close them. However, you can
tag them "fixed", by sending 'tag fixe
On Sun, Apr 07, 2002 at 02:26:30PM +0100, Will Newton wrote:
> On Saturday 06 Apr 2002 4:16 pm, Will Newton wrote:
>
> I have still not had any response to this. Can anyone tell me the correct
> procedure for getting these bugs closed?
>
> The changelog looks like this:
>
> ilisp (5.11.1-7) uns
On Saturday 06 Apr 2002 4:16 pm, Will Newton wrote:
I have still not had any response to this. Can anyone tell me the correct
procedure for getting these bugs closed?
The changelog looks like this:
ilisp (5.11.1-7) unstable; urgency=low
* well 125744 was fixed, but I put the files in the old
(I have CCd to debian-devel in case you are on holiday or otherwise
indisposed to close these)
ilisp is being removed from woody because of a bug that is fixed but not
closed. According to your changelog the following bugs are fixed, but are not
closed:
125744
140049
138669
137011
98132
12885
9 matches
Mail list logo