public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Al Bogner <al@usenet.pinguin.uni.cc>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: debug/9179: make modules: encode-gbk.o encode-gbk.c
Date: Tue, 07 Jan 2003 22:56:00 -0000	[thread overview]
Message-ID: <20030107225601.14384.qmail@sources.redhat.com> (raw)

The following reply was made to PR debug/9179; it has been noted by GNATS.

From: Al Bogner <al@usenet.pinguin.uni.cc>
To: bangerth@dealii.org,
 gcc-bugs@gcc.gnu.org,
 gcc-prs@gcc.gnu.org,
 nobody@gcc.gnu.org,
 gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: debug/9179: make modules: encode-gbk.o encode-gbk.c
Date: Tue, 7 Jan 2003 23:45:19 +0100

 On Dienstag, 7. Januar 2003 21:35 Wolfgang Bangerth wrote:
 
 > > Do I have to fear,  that my system could get problems, when I
 > > do a "make modules" without an install with the old
 > > configuration again?
 >
 > The time when I knew about Linux kernel configuration has gone
 > for more than half a decade, so I fear I can not be of any help.
 > Sorry.
 
 Hi Wolfgang,
 
 thanks for your answer. I am sorry too. As long as nobody can tell=20
 me exactly what do *without* disturbing my working system for sure,=20
 I do not want to do any changes with my system.
 
 Albert


             reply	other threads:[~2003-01-07 22:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 22:56 Al Bogner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-13 15:15 bangerth
2003-01-13 15:06 Al Bogner
2003-01-07 22:56 Wolfgang Bangerth
2003-01-07 15:26 Wolfgang Bangerth
2003-01-07 11:26 Al Bogner
2003-01-07  1:06 bangerth
2003-01-05 19:26 al

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=20030107225601.14384.qmail@sources.redhat.com \
    --to=al@usenet.pinguin.uni.cc \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).