Hi,
Reference:
> From: Tim Kientzle
> Date: Sat, 25 Jun 2011 09:41:36 -0700
> Message-id: <31d907f2-1f80-40b4-bdc3-486e3f988...@freebsd.org>
Tim Kientzle wrote:
> Thanks for the reminder Julian.
>
> I've just committed a fix to trunk that I'd appreciate if you could look at.
Thanks for the reminder Julian.
I've just committed a fix to trunk that I'd appreciate if you could look at.
> Might be nice if someone else would read through tar.
More eyes are always better! I'd especially appreciate help
improving the test suite for tar. I've put a lot of work into
the tes
FreeBSD tar has deficient error handling. I sent a fix 31 Jan 2011
http://www.freebsd.org/cgi/query-pr.cgi?pr=154407
Please commit the fix or write & commit a better fix.
As error codes ignored, I wonder if other poor coding may lurk in tar.
Might be nice if someone else would read thro
ut get anything wrong (case is sufficient)
>
> You get an error complaing about the security code.
>
> Press back. Your carefully edited PR is still there. Good.
>
> However, it displays the same image and the same security code as
> before, although send-pr seems to have
.
Press back. Your carefully edited PR is still there. Good.
However, it displays the same image and the same security code as
before, although send-pr seems to have generated a new one internally.
The new code is not displayed, however, since there is no expire
header on the old one and you just hit
> What is the proper method for submitting cores along with
> backtraces to the FreeBSD development team? Is it useful to
> submit cores, or is the backtrace sufficient?
Firstly, GNATS works over email and sending in a 4GB+ MIME
encoded core file could overload the mail servers of not
just th
Hello,
I have a few recent 5.3 panics I would like to submit. send-pr always bails
telling me that it is
out of space, despite the fact that the local filesystems have plenty of space
free:
pixie# send-pr -a ./backtrace -a ./uname-output -a ./messages -a
./sysctl-a-output -a
Hi,
Giorgos Keramidas wrote:
This means that it can take a while for someone to pick your report and
work on it; even then they might find the problem too difficult and just
leave it open for someone more knowledgeable.
Having said all this, what was your report about? Perhaps I can find it in
the
On 2004-08-22 21:37, Eitarou Kamo <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have sent the send-pr message. No one seems to work around to it.
> Doesn't anyone necessarily do it even if it were sent
When you use send-pr to submit a problem report, the report is saved in a
data
Eitarou Kamo <[EMAIL PROTECTED]> wrote
in <[EMAIL PROTECTED]>:
e-kamo> Hi,
e-kamo>
e-kamo> I have sent the send-pr message. No one seems to work
e-kamo> around to it.
e-kamo> Doesn't anyone necessarily do it even if it were sent
Please do not post thes
Hi,
(B
(BI have sent the send-pr message. No one seems to work
(Baround to it.
(BDoesn't anyone necessarily do it even if it were sent
(B
(B--
(B
(B***
(BEitarou Kamo
(B
(BTel. +81 75 703599
On Wed, Feb 11, 2004 at 01:14:46PM +0100, Friedemann Becker wrote:
> hello,
>
> I sent a new bugreport via the web interface and noticed two things I
> wondered about:
>
> - in the multiline forms it seems like there would be linebreaking
> when typing in the report, but on the website it show
hello,
I sent a new bugreport via the web interface and noticed two things I
wondered about:
- in the multiline forms it seems like there would be linebreaking
when typing in the report, but on the website it shows as one long line.
It's not very nice when you have to scroll around for every
On Wed, Jan 28, 2004 at 10:12:02AM -0800, Tim Kientzle wrote:
> Leo Bicknell wrote:
> >In a message written on Tue, Jan 27, 2004 at 01:47:57PM -0600, Brandon D.
> >Valentine wrote:
> >
> >>I'm afraid there's not much that FreeBSD can do about this. All PRs are
> >>forwarded to the public freebsd-
Leo Bicknell wrote:
In a message written on Tue, Jan 27, 2004 at 01:47:57PM -0600, Brandon D. Valentine wrote:
I'm afraid there's not much that FreeBSD can do about this. All PRs are
forwarded to the public freebsd-bugs mailing list ...
There's no reason the sender address needs to go to the mail
In a message written on Wed, Jan 28, 2004 at 04:38:54PM +0100, Dag-Erling Smørgrav
wrote:
> No, you need to realize that spam will happen no matter how careful
> you are, and take appropriate countermeasures.
Wearing a seatbelt and defensive driving are not mutually exclusive.
--
Leo Bic
Leo Bicknell <[EMAIL PROTECTED]> writes:
> That is, the sender address could be stored in the PR database,
> visable only to those who can change the status of a PR (I assume
> they have some password protected web/e-mail interface).
The PR database is distributed worldwide through cvsup.
> While
In a message written on Tue, Jan 27, 2004 at 01:47:57PM -0600, Brandon D. Valentine
wrote:
> I'm afraid there's not much that FreeBSD can do about this. All PRs are
> forwarded to the public freebsd-bugs mailing list and on any public
> mailing list there are inevitably n > 1 Microsoft clients su
reebsd-bugs mailing list and on any public
mailing list there are inevitably n > 1 Microsoft clients subscribed.
When using send-pr please always set the email address in the originator
field to a fully qualified address at which you will actively read mail
now and in the future. Filing a PR fr
helping newcomers on the
hackerscene
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Clifton
Royston
Verzonden: dinsdag 27 januari 2004 0:58
Aan: [EMAIL PROTECTED]
Onderwerp: [Freebsd-hackers] Yes, send-pr results in virus emails
OK, on January 23 I sent in a PR
OK, on January 23 I sent in a PR from a development-only machine
using the send-pr command. This machine happens to actually receive
mail because I'm testing mail server software on it, but I have never
used it to send mail, and I have never gotten mail on that machine
other than via se
Giorgos Keramidas <[EMAIL PROTECTED]> writes:
> You can clearly see that (in line 3), I have chosen to view only PRs
> whose state is `open' AND (line 2) severity is `critical', in an
> effort to help closing first those PRs that are more important.
Just ignore the severity and priority. They ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 13 June 2001 8:57 pm, Giorgos Keramidas wrote:
> I have a few hours to spare tonight, and I was using the
> query-pr-summary.cgi script to view the open PRs.
[snip]
Looks like this has been resolved. However, if this is something you
On Wed, Jun 13, 2001 at 10:06:47PM -0700, Dima Dorfman wrote:
> Is it possible that the PR was closed between the time when you
> requested the summary and the time when you requested full information
> on the PR?
No, it was my silliness. While I was viewing the PR summary, pr=28002
changed sta
Giorgos Keramidas <[EMAIL PROTECTED]> writes:
> I have a few hours to spare tonight, and I was using the
> query-pr-summary.cgi script to view the open PRs.
>
> The query URL was (wrapped to avoid terminal silliness):
>
> 1 http://www.FreeBSD.org/cgi/query-pr-summary.cgi?\
> 2 category=&se
I have a few hours to spare tonight, and I was using the
query-pr-summary.cgi script to view the open PRs.
The query URL was (wrapped to avoid terminal silliness):
1 http://www.FreeBSD.org/cgi/query-pr-summary.cgi?\
2 category=&severity=critical&priority=&class=\
3 &state=open&sort=cate
Oh almight source hackers,
I'm writing an article on how to use send-pr, based on gleanings from
this list and others over the years. Since wrong advice there could
easily generate a lot of lousy PRs, I was hoping one or two of you
folks who actually *read* PRs might be willing to review i
27 matches
Mail list logo
