From: Hans Reiser <reiser@namesys.com>
To: David Masover <ninja@slaphack.com>
Cc: Peter van Hardenberg <pvh@uvic.ca>,
Jonathan Sailor <jsailor@jesnetplus.com>,
reiserfs-list@namesys.com,
Yoanis Gil Delgado <fred@lab.matcom.uh.cu>
Subject: Re: Authoring a versioning plugin
Date: Sat, 14 Jan 2006 14:23:29 -0800 [thread overview]
Message-ID: <43C979E1.9080405@namesys.com> (raw)
In-Reply-To: <43C934D3.7040406@slaphack.com>
David Masover wrote:
>Peter van Hardenberg wrote:
>
>
>>On January 13, 2006 03:00 pm, you wrote:
>>
>>
>>
>>>On Fri, 13 Jan 2006, Hans Reiser wrote:
>>>
>>>
>>>
>>>>If someone figures out why we can't do it but /proc can, or even fixes
>>>>it, it would be good.
>>>>
>>>>
>>>It wouldn't be something so simple as echo's trailing newline, would it?
>>>
>>>-Jonathan
>>>
>>>
>>Good thought, but no:
>>
>>
>[...]
>
>
>>norbs@cortana:/home/norbs/reiser/emptydir/..../plugin$ echo "ext-1" -n >
>>fibration
>>
>>
>[...]
>
>
>>norbs@cortana:/home/norbs/reiser/emptydir/..../plugin$ irb
>>irb(main):004:0> f = open('fibration', 'w')
>>=> #<File:fibration>
>>irb(main):005:0> f.write('ext-1')
>>=> 5
>>irb(main):006:0> f.close
>>=> nil
>>irb(main):007:0> exit
>>
>>
>[...]
>
>
>>I'd look more closely at how proc does it and how we do it, but I'm too tired
>>for source digging tonight.
>>
>>
>
>I think the difference is that Reiser expects a null-terminated string,
>
>
I'll happily take a patch to fix that.....
>whereas Proc doesn't need the null, and can chop off newlines when needed.
>
>So, I think this would also work:
>
>echo -en 'ext-1\0' > fibration
>
>
>
>
>
prev parent reply other threads:[~2006-01-14 22:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 22:59 Authoring a versioning plugin Yoanis Gil Delgado
2006-01-12 4:09 ` Hans Reiser
2006-01-12 6:44 ` Hans Reiser
2006-01-12 16:33 ` Jonathan Briggs
2006-01-12 18:33 ` Bedros Hanounik
[not found] ` <200601121502.32227.fred@lab.matcom.uh.cu>
2006-01-12 20:08 ` Yoanis Gil Delgado
2006-01-12 21:48 ` David Masover
2006-01-12 22:43 ` Bedros Hanounik
[not found] ` <200601121856.00665.fred@lab.matcom.uh.cu>
2006-01-12 23:56 ` Yoanis Gil Delgado
2006-01-13 20:59 ` Hans Reiser
2006-01-13 16:43 ` David Masover
[not found] ` <200601121434.54881.fred@lab.matcom.uh.cu>
2006-01-12 20:05 ` Yoanis Gil Delgado
2006-01-12 19:13 ` Mike Benoit
2006-01-12 18:14 ` Peter van Hardenberg
[not found] ` <200601121439.09483.fred@lab.matcom.uh.cu>
2006-01-12 20:06 ` Yoanis Gil Delgado
2006-01-12 21:58 ` David Masover
2006-01-13 20:34 ` Hans Reiser
2006-01-13 21:17 ` Toomas Laasik
2006-01-13 21:48 ` Hans Reiser
2006-01-14 11:56 ` Pierre Etchemaïté
2006-01-13 23:00 ` Jonathan Sailor
2006-01-14 9:07 ` Peter van Hardenberg
2006-01-14 17:28 ` David Masover
2006-01-14 22:23 ` Hans Reiser [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=43C979E1.9080405@namesys.com \
--to=reiser@namesys.com \
--cc=fred@lab.matcom.uh.cu \
--cc=jsailor@jesnetplus.com \
--cc=ninja@slaphack.com \
--cc=pvh@uvic.ca \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.