From: Blaisorblade <blaisorblade@yahoo.it>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
kbuild-devel@lists.sourceforge.net
Subject: Re: [patch 1/1] kconfig: trivial cleanup
Date: Tue, 31 May 2005 22:35:34 +0200 [thread overview]
Message-ID: <200505312235.35234.blaisorblade@yahoo.it> (raw)
In-Reply-To: <Pine.LNX.4.61.0505311123310.3728@scrub.home>
On Tuesday 31 May 2005 11:27, Roman Zippel wrote:
> Hi,
>
> On Sun, 29 May 2005 blaisorblade@yahoo.it wrote:
> > If you want, I'll do one patch update the included version to 2.0 Bison
> > (which uses an updated skeleton) and then, separately, a patch updating
> > zconf.tab.c_shipped to reflect the updated zconf.y.
> I'd prefer to patch the changes into zconf.tab.c_shipped directly. At some
> point it should be regenerated, but I'd like to avoid it and only do it if
> the parser itself needs a change.
I can regenerate it only with bison 2.0, since that's what I have installed.
So if you don't want it to be regenerated, you cannot accept my patch. I
proposed sending two patches to avoid mixing the bison changes with this
patch changes, that's all.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Messenger: chiamate gratuite in tutto il mondo
http://it.beta.messenger.yahoo.com
next prev parent reply other threads:[~2005-05-31 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 17:45 blaisorblade
2005-05-31 9:27 ` Roman Zippel
2005-05-31 20:35 ` Blaisorblade [this message]
2005-05-31 23:50 ` Roman Zippel
2005-06-01 16:11 ` Blaisorblade
-- strict thread matches above, loose matches on Subject: below --
2005-03-22 16:36 blaisorblade
2005-03-22 19:27 ` 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=200505312235.35234.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®