Peter Palfrader wrote:
>
>> I think a point could be made for including a bogus bug in a
>> guy's first package so he can learn the changelog procedure for
>> closing it while he's still in close contact with his sponsor.
>
> Since ITPs are now reported as bugs against wnpp you have your
> traini
Hi Rick!
On Fri, 15 Sep 2000, Rick Younie wrote:
> I think a point could be made for including a bogus bug in a
> guy's first package so he can learn the changelog procedure for
> closing it while he's still in close contact with his sponsor.
Since ITPs are now reported as bugs against wnpp you
Peter Palfrader wrote:
>
>> I think a point could be made for including a bogus bug in a
>> guy's first package so he can learn the changelog procedure for
>> closing it while he's still in close contact with his sponsor.
>
> Since ITPs are now reported as bugs against wnpp you have your
> train
Antti-Juhani Kaijanaho wrote:
> On 2914T102042-0700, Rick Younie wrote:
>> Anyhow, ignore this specific example. I just mean in the general
>> case. Get it close or flog the package until it squeaks?
>
> Well, in the final analysis, it's the sponsor's neck on the line if
> something bad happ
Hi Rick!
On Fri, 15 Sep 2000, Rick Younie wrote:
> I think a point could be made for including a bogus bug in a
> guy's first package so he can learn the changelog procedure for
> closing it while he's still in close contact with his sponsor.
Since ITPs are now reported as bugs against wnpp you
Antti-Juhani Kaijanaho wrote:
> On 2914T102042-0700, Rick Younie wrote:
>> Anyhow, ignore this specific example. I just mean in the general
>> case. Get it close or flog the package until it squeaks?
>
> Well, in the final analysis, it's the sponsor's neck on the line if
> something bad hap
6 matches
Mail list logo
