From: Randy Dunlap <rdunlap@infradead.org>
To: Matt Hardcastle <m@hardcastle.com>, linux-kernel@vger.kernel.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
drepper@redhat.com, Jan-Benedict Glaw <jbglaw@lug-owl.de>,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: [RFC] reconsider [PATCH] hostname up to 255 character
Date: Thu, 24 Jun 2021 18:53:54 -0700 [thread overview]
Message-ID: <7f5cbd89-7008-7da7-2329-8b91753a02d1@infradead.org> (raw)
In-Reply-To: <A27A5542-69CD-4B7F-86C5-6940179988B0@hardcastle.com>
On 6/23/21 12:16 PM, Matt Hardcastle wrote:
> Hi,
>
> In 2006 Randy Dunlap submitted a patch [^1] to increase the supported hostname length to 255 characters. There was some discussion on the patch, but it appeared to go stale.
>
> Are you open to reconsidering the change?
>
> - m@
>
> ^1 https://lore.kernel.org/lkml/20060525204534.4068e730.rdunlap@xenotime.net/
>
Hi,
Thanks for bringing this back up. Very few people read/reply to LKML unless
they are Cc-ed on the email, so I'll add a few Cc's here.
--
~Randy
prev parent reply other threads:[~2021-06-25 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 19:16 [RFC] reconsider [PATCH] hostname up to 255 character Matt Hardcastle
2021-06-25 1:53 ` Randy Dunlap [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=7f5cbd89-7008-7da7-2329-8b91753a02d1@infradead.org \
--to=rdunlap@infradead.org \
--cc=drepper@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jbglaw@lug-owl.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m@hardcastle.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;
as well as URLs for NNTP newsgroup(s).