From: cinap_lenrek@gmx.de
To: 9front@googlegroups.com
Subject: Re: todo
Date: Fri, 1 Apr 2011 09:13:06 +0200 [thread overview]
Message-ID: <b91861b65b96bba6e98d507246aae189@gmx.de> (raw)
In-Reply-To: <AANLkTi=x_WhkmQbxD9Fd6a8p3REieek_J7tcv_n8um2J@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 116 bytes --]
why? can't we just fire and forget? server that dont know the
command will just reply with an error no?
--
cinap
[-- Attachment #2: Type: message/rfc822, Size: 5454 bytes --]
From: Uriel <uriel@berlinblue.org>
To: 9front@googlegroups.com
Subject: Re: todo
Date: Fri, 1 Apr 2011 00:04:18 -0700
Message-ID: <AANLkTi=x_WhkmQbxD9Fd6a8p3REieek_J7tcv_n8um2J@mail.gmail.com>
On Thu, Mar 31, 2011 at 9:40 PM, aiju <aiju@phicode.de> wrote:
>
>> This is plain gratuitous idiotic protocol breaking, you can do the
>> same thing simply by providing an alternative attach name with ctl
>> file(s) for fancy things like moving stuff around.
>
> It doesn't break the protocol at all: Clients which don't need it
> don't have to know about it and if the server doesn't have it the
> client can emulate it.
But then the client has to negotiate with the server to find out if it
supports the Tmove extension,
it is totally idiotic and retarded, adding it via an alternative
attach name is trivial and doesn't break any shit.
uriel
next prev parent reply other threads:[~2011-04-01 7:13 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 ` cinap_lenrek [this message]
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 ` todo Ethan Grammatikidis
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=b91861b65b96bba6e98d507246aae189@gmx.de \
--to=cinap_lenrek@gmx.de \
--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).