public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net,
	Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] udev 016 release
Date: Thu, 12 Feb 2004 00:27:09 +0200	[thread overview]
Message-ID: <1076538429.22542.12.camel@nosferatu.lan> (raw)
In-Reply-To: <20040211221324.GC14231@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

On Thu, 2004-02-12 at 00:13, Greg KH wrote:
> On Tue, Feb 03, 2004 at 11:43:22PM +0200, Martin Schlemmer wrote:
> > On Tue, 2004-02-03 at 22:13, Greg KH wrote:
> > 
> > Once again, patch to make logging a config option.
> > 
> > Reason for this (since you asked for it =):
> > - In our setup it is easy (although still annoying) .. just
> > edit the ebuild, add logging support (or remove it) and rebuild.
> > For say a binary distro, having the logging is useful for debugging
> > some times, but its more a once of, or rare thing, as you do not
> > add or change config files every day.  Sure, we can have logging
> > by default, but many do not want ~300 lines of extra debugging in
> > their logs is not pleasant, and they will complain.  Rebuilding
> > the package for that binary package (given the users it is targeted
> > to) is usually not within most users grasp.
> 
> Ok, I applied this patch.
> 
> And then I went back and fixed it so it actually would work :(
> 
> Here's the changes I had to make to get everything to build properly,
> and to let us have a boolean type for the config files.
> 

Interest sake ... when did it actually fail?  (When linking with
klibc maybe?  Been using here without problems).


Thanks,

-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-11 22:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 20:13 [ANNOUNCE] udev 016 release Greg KH
2004-02-03 20:49 ` Martin Schlemmer
2004-02-03 23:14   ` Greg KH
2004-02-03 21:28 ` Martin Schlemmer
2004-02-03 23:03   ` Martin Schlemmer
2004-02-03 23:13     ` Greg KH
2004-02-04  0:01       ` Kay Sievers
2004-02-04  4:25       ` Martin Schlemmer
2004-02-08 11:27         ` Martin Schlemmer
2004-02-08 13:01           ` Martin Schlemmer
2004-02-03 21:43 ` Martin Schlemmer
2004-02-11 22:13   ` Greg KH
2004-02-11 22:27     ` Martin Schlemmer [this message]
2004-02-12  1:19       ` Greg KH

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=1076538429.22542.12.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox