From: "David S. Miller" <davem@redhat.com>
To: zaitcev@redhat.com
Cc: kai-germaschewski@uiowa.edu, willy@debian.org,
linux-kernel@vger.kernel.org
Subject: Re: invalid character 45 in exportstr for include-config
Date: Sun, 03 Nov 2002 22:50:36 -0800 (PST) [thread overview]
Message-ID: <20021103.225036.99063973.davem@redhat.com> (raw)
In-Reply-To: <20021103142223.A10629@devserv.devel.redhat.com>
From: Pete Zaitcev <zaitcev@redhat.com>
Date: Sun, 3 Nov 2002 14:22:23 -0500
> Makes me wonder if Pete's exporting of 'INIT-Y' is a good idea, you may
> want to change that to '_' as well.
Sorry about that. It's already submitted, so I'll wait until
it recycles through Dave's tree then change it. Thanks for letting
me know, Kai.
None of your patches are applied yes, please feel free to submit
a new batch and I will wait for that.
prev parent reply other threads:[~2002-11-04 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 3:18 invalid character 45 in exportstr for include-config Matthew Wilcox
2002-11-03 6:20 ` David S. Miller
2002-11-03 7:40 ` Keith Owens
2002-11-03 19:17 ` Kai Germaschewski
2002-11-03 19:22 ` Pete Zaitcev
2002-11-04 6:50 ` David S. Miller [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=20021103.225036.99063973.davem@redhat.com \
--to=davem@redhat.com \
--cc=kai-germaschewski@uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.org \
--cc=zaitcev@redhat.com \
/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