From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Kai Makisara <Kai.Makisara@kolumbus.fi>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] make st seekable again
Date: Thu, 10 Mar 2005 17:58:37 +0000 [thread overview]
Message-ID: <1110477516.28860.298.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.3.96.1050310114027.11549B-100000@gatekeeper.tmr.com>
On Iau, 2005-03-10 at 16:56, Bill Davidsen wrote:
> - leave it the way it is
> - fix the hole and break tar
> - wait for FSF to fix tar, then fix the hole
> - try to fix it without breaking tar, which may not be really possible
> and could leave part of the problem and still break tar somehow
> - fix it, and leave the admin a way to build a kernel with the hole other
> than just reverting the fix
If we "fix" it the FSF will probably take years. If your vendor can't
produce a fixed tar when asked and the issue comes up, get a better
vendor ;)
Alan
next prev parent reply other threads:[~2005-03-10 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503081911.j28JBlxi016013@hera.kernel.org>
2005-03-09 20:51 ` [PATCH] make st seekable again Alan Cox
2005-03-09 21:58 ` Kai Makisara
2005-03-09 22:27 ` Alan Cox
2005-03-10 11:49 ` Bill Davidsen
2005-03-10 12:10 ` Arjan van de Ven
2005-03-10 16:43 ` Alan Cox
2005-03-10 16:56 ` Bill Davidsen
2005-03-10 17:13 ` Arjan van de Ven
2005-03-10 17:58 ` Alan Cox [this message]
[not found] <fa.i3f7d9s.30m8rg@ifi.uio.no>
[not found] ` <fa.l4kuq52.e6001g@ifi.uio.no>
2005-03-10 0:43 ` Bodo Eggert
2005-03-10 20:01 ` Willy Tarreau
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=1110477516.28860.298.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Kai.Makisara@kolumbus.fi \
--cc=arjan@infradead.org \
--cc=davidsen@tmr.com \
--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