From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@googlegroups.com
Subject: Re: todo
Date: Fri, 1 Apr 2011 14:36:47 +0100 [thread overview]
Message-ID: <3D60FF7C-95CB-4DB1-9249-D31FE1C9A47D@fastmail.fm> (raw)
In-Reply-To: <a3a823481515787ec2342cd5280c0ce3@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]
On 1 Apr 2011, at 12:38 pm, cinap_lenrek@gmx.de wrote:
>
> maybe we can live with a special fscmd and let the user figure out
> the right filsys name and path? we can make the command format
> and naming compatible so it works consistently with kfs, cwfs and
> kenfs.
This sounds like it could be a bitch if it's 2 in the morning and you
just want to move those few videos you just downloaded to their
proper place before going to sleep.
>> From: Uriel <uriel@berlinblue.org>
>>
>> Changing the protocol for this is just stupid, next you will find a
>> trillion equally good reasons to add other extensions.
Ah, the time-honoured argument against change. :] Move is not just
any extension. It doesn't exist for some flaky transient piece of
bullshit software that will be forgotten in 5 years time. It exists
because storage space has grown faster than storage speed. Not just
space, storage use has grown faster than the speed.
Then there's the idea of a unified interface to your files. A special
extra file to do a special operation (which move really ought not to
be) breaks unity and consistency. mv is one of the fundamental file
operations, and I for one REALLY don't want it trying to find some
3rd file to send messages to... That's got to be flakey at best,
hasn't it? Also it kinda reeks of .git / .hg. If you're working in a
subdir of a git repo, git very graciously looks up the tree until it
finds .git, but if you try to include one git repo inside another it
breaks.
There's another thing: How _hard_ will Tmove break anything? How much
trouble will it be to fix everything to fail gracefully, either for
any bad message or just for Tmove (whichever is easier)? Granted,
"old software" isn't necessarily included in "everything" but how
much work will it be to find and look into every server in /sys/src/cmd?
[-- Attachment #2: Type: text/html, Size: 3296 bytes --]
next prev parent reply other threads:[~2011-04-01 13:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <405d44d0ddf24c71ff94c72804f03bec@gmx.de>
2011-03-30 20:57 ` todo Stanley Lieber
2011-03-30 22:39 ` todo cinap_lenrek
2011-03-30 22:46 ` todo Stanley Lieber
2011-03-30 22:04 ` todo uriel
2011-04-01 0:30 ` todo Ethan Grammatikidis
2011-04-01 0:47 ` todo Jacob Todd
2011-04-01 0:59 ` todo Uriel
2011-04-01 1:12 ` todo Ethan Grammatikidis
2011-04-01 4:40 ` todo aiju
2011-04-01 7:04 ` todo Uriel
2011-04-01 7:13 ` todo cinap_lenrek
2011-04-01 9:30 ` todo Uriel
2011-04-01 10:18 ` todo cinap_lenrek
2011-04-01 10:24 ` todo Uriel
2011-04-01 11:38 ` todo cinap_lenrek
2011-04-01 13:36 ` Ethan Grammatikidis [this message]
2011-04-01 13:54 ` todo Julius Schmidt
2011-04-01 17:41 ` todo Uriel
2011-04-01 19:02 ` todo Ethan Grammatikidis
2011-04-02 14:22 ` todo aiju
2011-04-02 14:52 ` todo Ethan Grammatikidis
2011-04-01 17:38 ` todo Uriel
2011-04-01 7:09 ` todo cinap_lenrek
2011-04-01 6:14 ` todo Taru Karttunen
2011-05-02 7:30 TODO Uriel
2011-05-02 13:25 ` TODO Julius Schmidt
2011-05-02 17:03 ` TODO Uriel
2011-05-02 18:24 ` TODO Iruatã Souza
2011-05-02 19:33 ` TODO ron minnich
2011-05-02 13:45 ` TODO Jacob Todd
2018-02-24 19:53 TODO Kurt H Maier
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=3D60FF7C-95CB-4DB1-9249-D31FE1C9A47D@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=9front@googlegroups.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).