All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Ildar Muslukhov <ildarm@google.com>
Cc: trinity@vger.kernel.org
Subject: Re: Patch suggestion - logs cleanup
Date: Wed, 2 Oct 2013 20:11:57 -0400	[thread overview]
Message-ID: <20131003001157.GA17386@redhat.com> (raw)
In-Reply-To: <CAEGbLtsZfQXE1Qs+5ruEsJwaSdeJ0upeoW0qnEOrAk3RRdZ6YQ@mail.gmail.com>

On Wed, Oct 02, 2013 at 05:04:50PM -0700, Ildar Muslukhov wrote:
 > How about cleaning up source from all the printf and converting them
 > to the output? I am willing to do that, since would like to have more
 > control over logging and output.

yeah, worth doing. Careful though, some of the printf's happen before we've opened
the log files.

Sort of related: At some point I think debugf needs to log to a separate debug log file.

	Dave

  reply	other threads:[~2013-10-03  0:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03  0:04 Patch suggestion - logs cleanup Ildar Muslukhov
2013-10-03  0:11 ` Dave Jones [this message]
2013-10-03 17:31   ` Ildar Muslukhov
2013-10-03 17:50     ` Dave Jones
2013-10-04 19:34       ` Ildar Muslukhov
2013-10-04 20:05         ` Dave Jones
2013-10-04 20:07           ` Ildar Muslukhov

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=20131003001157.GA17386@redhat.com \
    --to=davej@redhat.com \
    --cc=ildarm@google.com \
    --cc=trinity@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.