Re: Closable list of PRs (duplicate copy for this list)

> ----- Original Message -----
> From: Dag-Erling Smorgrav <[email protected]>
> Date: Tuesday, March 19, 2002 2:02 am
> Subject: Re: Closable list of PRs (duplicate copy for this list)
>
> [sorry for the delay in answering to this]

No Problem. :)

> > "Hiten Pandya" <[email protected]> writes:
> > misc/34039 (FreeBSD fortune(6) tips to be added)
> 
> Not closable unless a) the patch has been committed or rejected or b)
> you (as the originator) are withdrawing it.

Understood.  You mean, only PRs which have a patch committed, or are rejected
for some reason can be closed.  I get it. :)

> > docs/34074 (Incomplete disklabel instructions)
> Why is this PR closable?

It has stalled for a long time, and no one has been trying to pass anymore
feedback to it.  Basically, the originator needs to be reminded.

> > docs/34038 (New Article for the a.out to ELF upgrade process [in 
> > detail])
> 
> Why is this PR closable?

It has an interesting, and a needed article for FreeBSD.

> > docs/32468 (broken link in handbook: sysutils/mkisofs - [tmp. fix])
> Why is this PR closable?

It has stalled.  Peter said he will look into it Later on Today, but it
seems nothing has happened till _today_.  Maybe to mark it under a feedback,
or analysed state.

> > kern/26510 (panic Intel STL2 server board with 4GB RAM)
> Why is this PR closable?  Sheldon makes a good argument for 
> keeping it
> open.

The 4G issue is resolvable now, as there is the KVA_PAGES option 
in FreeBSD.  I had a personal discussion with Sheldon, and he said that it
would be better if this PR was assigned to Matt, and also, I gave him the
Message-IDs for the post which Terry made on how to resolve the 4G issue
the hard way and the easy way. 

I will document this in the kernel configuration chapter, if needed.  What
do you think?

> > i386/26812 (old bootstrap /sys/i386/boot/... still in -STABLE 
> branch)
> Has this issue been resolved?  In any case, the PR is assigned to
> peter; you should contact him about closing it.

Understood.

> > docs/32020 (loader.8 manpage missing tunables)
> As Bruce pointed out, this PR should not be closed yet - unless your
> article is finished and has been committed.

I will talk to Bruce on what to do with this PR, as he hasn't told me on
what needs to be documented.  I did try and document the maxusers tunable
but the autosizing addition broke my patch.

> > i386/26736 (System freeze booting from (i386) 4.3 floppies)
> Why is this PR closable?  Has the originator confirmed that his
> problem has been solved?

Aha, the PR was put into 'feedback' state, but I think Sheldon forgot
to CC the copy of that status change to the Originator, or is this done
automatically when the state is changed?

> > i386/34399 (Undefined datatypes in netinet headers)
> > [ the above PR can be closed, according to the followup, I checked
> > the header file src/netinet/in_systm.h, as well write code. ]
> This PR is assigned to dwmalone; contact him about closing it.

Understood.

> > kern/28162 ([4G Memory Problem] - fixed in RELENG_4, HEAD, 4.5])
> Have the patches in question been committed?  If not, the PR should
> not be closed.

The patches are not committed, because I think this PR was forgotten
by the developers.  According to what Matt told me on the cvs-all list
was "to leave all VM related changes to him", because of his experience
in that part of the field.  In a nutshell, this PR IMHO should be assigned
to Matt for further investigation on this issue.  The most closest I got
to the fix provided is revision 1.130.2.11 on sys/vm/swap_pager.c

> > i386/29096 ([no feedback from originator])
> Too fresh.

I will email the originator (cc: bug-followup@), and see what he has to
say. :)

> > i386/33089 ([no feedback from originator])
> Absolutely not.

Do you think I should ask the re@ team on what to do with this PR?

> > i386/34051 ([not enought information - looks misfiled to me])
> No, it is not misfiled, but it is certainly incomplete and should be
> closed in a month or two if the originator doesn't respond to your
> questions.

Shall I remind the user about this, or is it un-neccessary?

> > i386/28536 ([needs to be handed over to the MSDOSFS maintainer])
> Not closable, unless the patch in the PR (or a similar patch obtained
> from NetBSD) has been committed.

I will see what I can do with this.

> In the future, please refrain from suggesting that a PR is closable
> without explaining why you think it is.

Understood.  As now I understand what type of PRs can be _closed_ by the
bugbusters@ list. Sorry for any inconvenience. :-)  Do you think there can
be any possibility for the GNATS DB, to automatically send email to the
originator if a PR has been inactive for a specified timeframe?

Regards,

  -- Hiten

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/

To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-bugbusters" in the body of the message