From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] logging and internal API changes in next
Date: Mon, 17 Aug 2009 16:31:22 -0400 [thread overview]
Message-ID: <1250541071-sup-7690@Longbow> (raw)
In-Reply-To: <1250538107-sup-7121@masanjin.net>
Excerpts from William Morgan's message of Mon Aug 17 15:50:52 -0400 2009:
> Dear Suppers,
>
> I've merged the aforementioned internal API changes, and a pretty big
> rewrite of the logging system (branch "logging"), into next. It works
> for me, but please report any problems you see.
>
> All logging messages are now categorized by level (debug, info, warn,
> error) and will only be output when the global logging level is <= the
> message level. The global logging level is determined by the environment
> variable SUP_LOG_LEVEL; when unset, the default is "info". You'll notice
> that the majority of the messages you saw before are now "debug"
> messages, so the log buffer is much quieter.
>
> This change also applies to the various sup-* scripts.
>
> If you use this code and then switch to a branch without these changes,
> you may encounter errors because labels are now represented on disk as
> Sets instead of arrays. The solution is to edit your sources.yaml file
> and manually change the Sets back to arrays; it should be obvious how to
> do this. I don't anticipate this affecting too many people. If it does,
> we can transform labels to arrays before storing to make this easier,
> but hopefully it's just a temporary issue.
>
> I would like to merge these changes down to master sooner rather than
> later, because they're so far-reaching.
Looking forward to it, thanks.
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)
prev parent reply other threads:[~2009-08-17 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 19:50 William Morgan
2009-08-17 20:31 ` Andrei Thorp [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=1250541071-sup-7690@Longbow \
--to=garoth@gmail.com \
/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