linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Michael Buesch <fsdeveloper@yahoo.de>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix menuconfig if saving on different fs
Date: Wed, 28 May 2003 18:41:34 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0305281837500.5042-100000@serv> (raw)
In-Reply-To: <200305262135.25363.fsdeveloper@yahoo.de>

Hi,

On Mon, 26 May 2003, Michael Buesch wrote:

> +			while ((l = fgetc(out)) != EOF) {
> +				if (fputc(l, out_new) == EOF) {
> +					fclose(out);
> +					fclose(out_new);
> +					return 1;
> +				}

I don't really like this file copy, I'd rather create the file in the 
destination directory. I fixed this here a bit different.

bye, Roman


      reply	other threads:[~2003-05-28 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 19:35 [PATCH] fix menuconfig if saving on different fs Michael Buesch
2003-05-28 16:41 ` Roman Zippel [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=Pine.LNX.4.44.0305281837500.5042-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=fsdeveloper@yahoo.de \
    --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;
as well as URLs for NNTP newsgroup(s).