mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	Sam Ravnborg <sam@ravnborg.org>,
	Kai Germaschewski <kai-germaschewski@uiowa.edu>,
	<linux-kernel@vger.kernel.org>
Subject: Re: 2.5: troubles with piping make output
Date: Sun, 3 Nov 2002 21:54:05 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211032146240.6949-100000@serv> (raw)
In-Reply-To: <20021103202446.F5589@flint.arm.linux.org.uk>

Hi,

On Sun, 3 Nov 2002, Russell King wrote:

> No thanks.  That breaks my build scripts.  I don't want to go logging into
> multiple machines just to run make oldconfig when the old system worked
> perfectly well.
> 
> "perfectly well" here means that make oldconfig worked over ssh, with the
> local end logging the stdout to a file as well as the terminal, with stdin
> from the terminal.  It is quite reasonable to expect the configuration to
> continue as normal.

Huh? What do you mean? oldconfig still works as before, above only happens 
if you touch .config or a Kconfig file, kconfig tries to automatically 
update .config and will fail if stdio is redirected, but needs user input.
The problem is not a missing fflush, the question is why kconfig couldn't 
detect the pipe.

bye, Roman


  reply	other threads:[~2002-11-03 20:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-03 16:14 Denis Vlasenko
2002-11-03 18:28 ` Sam Ravnborg
2002-11-04  0:38   ` Denis Vlasenko
2002-11-03 20:10     ` Roman Zippel
2002-11-03 20:24       ` Russell King
2002-11-03 20:54         ` Roman Zippel [this message]
2002-11-03 21:24           ` Russell King
2002-11-03 21:29             ` Roman Zippel
2002-11-03 21:39               ` Russell King
2002-11-03 21:55                 ` Roman Zippel

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=Pine.LNX.4.44.0211032146240.6949-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=kai-germaschewski@uiowa.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=sam@ravnborg.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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

all inboxes | Powered by JetHome®