[OpenAFS-devel] Issues with my precache patch (was: Documentation
for fs precache)
Phillip Moore
w.phillip.moore@gmail.com
Tue, 19 Oct 2010 15:30:55 -0400
--0015175cd5dae947090492fd54d8
Content-Type: text/plain; charset=ISO-8859-1
This has turned from a simple, 30 minute patch into a lot more effort than I
am willing to put into it right now, all to fix something I don't even use,
personally.
I'm afraid I'm putting this one on a back burner for now.
On Tue, Oct 19, 2010 at 2:36 PM, Derrick Brashear <shadow@gmail.com> wrote:
> On Tue, Oct 19, 2010 at 2:21 PM, Phillip Moore
> <w.phillip.moore@gmail.com> wrote:
> >
> > Well, if this simple patch to the current pioctl can be made without all
> > that overhead, then someone else can fix this, unfortunately. I thought
> > this would be relatively simple, and it's a fix I don't really need
> > personally. Sorry to be selfish...
> > The real question is: do I need a new pioctl for this? I'm just
> modifying
> > the existing code and changing it's behavior.
>
> which is precisely why you need a new pioctl. which isn't that hard.
> just mail the registrar and ask for the next one.
>
--0015175cd5dae947090492fd54d8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div><br></div>This has turned from a simple, 30 minute patch into a lot mo=
re effort than I am willing to put into it right now, all to fix something =
I don't even use, personally.<div><br></div><div>I'm afraid I'm=
putting this one on a back burner for now.<br>
<br><div class=3D"gmail_quote">On Tue, Oct 19, 2010 at 2:36 PM, Derrick Bra=
shear <span dir=3D"ltr"><<a href=3D"mailto:shadow@gmail.com">shadow@gmai=
l.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Tue, Oct 19, 2010 at 2:21 PM, Phillip Moore<br>
<div class=3D"im"><<a href=3D"mailto:w.phillip.moore@gmail.com">w.philli=
p.moore@gmail.com</a>> wrote:<br>
><br>
</div><div class=3D"im">> Well, if this simple patch to the current pioc=
tl can be made without all<br>
> that overhead, then someone else can fix this, unfortunately. =A0I tho=
ught<br>
> this would be relatively simple, and it's a fix I don't really=
need<br>
> personally. =A0Sorry to be selfish...<br>
> The real question is: do I need a new pioctl for this? =A0I'm just=
modifying<br>
> the existing code and changing it's behavior.<br>
<br>
</div>which is precisely why you need a new pioctl. which isn't that ha=
rd.<br>
just mail the registrar and ask for the next one.<br>
</blockquote></div><br></div>
--0015175cd5dae947090492fd54d8--