From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] edbrowse erroneously prints a warning on receiving a...
Date: Tue, 17 Feb 2015 21:12:53 +0000 [thread overview]
Message-ID: <20150217211253.GA32332@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150117093045.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Tue, Feb 17, 2015 at 09:30:45AM -0500, Karl Dahlke wrote:
> > warning: http error 201, CreatedAccepted
>
> I would suggest not printing this error, unless debug >= 3.
> I'm trying to keep 0 1 and 2 as reasonable debug levels for the average user,
> and 3 or higher is for developers.
> (After ten years I'm finally coming up with a system.)
> So we would want to see this but it really doesn't mean anything to the user.
> This would be a quick change in http.c.
It's also *not* a warning if you get a 2* code like this, it actually indicates success.
> As we move forward, developing 3.5.4,
> we should again change the version to 3.5.4.something.
> Chris I'll leave that one to you, since you had some thoughts
> on version strings etc, and I mostly don't care.
Before we do this, do we want to decide what is going to go in the next version
and whether that wants to stay a 3.5 (or even really a 3 for that matter).
With the DOM changes planned I'd be thinking at least of 3.6.0 for the next
release.
This'd make the next version string 3.6.0.dev (or something like that).
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-02-17 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 14:30 Karl Dahlke
2015-02-17 21:12 ` Adam Thompson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150217211253.GA32332@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).