From: Jim Blandy <jimb@codesourcery.com>
To: gdb@sourceware.org
Subject: Re: RFC: File transfer commands
Date: Thu, 01 Nov 2007 00:24:00 -0000 [thread overview]
Message-ID: <m33avq3j99.fsf@codesourcery.com> (raw)
In-Reply-To: <20071030184140.GA6970@caradoc.them.org> (Daniel Jacobowitz's message of "Tue, 30 Oct 2007 14:41:40 -0400")
Daniel Jacobowitz <drow at false.org> writes:
> On Tue, Oct 30, 2007 at 11:29:12AM -0700, Jim Blandy wrote:
>> Yeah, 'remote ls' seems like the logical missing piece. Why not use
>> 'vFile:' as the prefix for delete, and qXfer for read and write?
>
> No preference really besides bikeshed. More consistency with qXfer,
> less with other file operations. Is the annex the filename or an open
> file descriptor?
It's not a big deal to me at all. I think the person hashing out the
details, writing the docs, and doing the implementation gets to make
the call.
next prev parent reply other threads:[~2007-11-01 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 19:55 Daniel Jacobowitz
2007-10-29 20:29 ` Ulrich Weigand
2007-10-29 20:40 ` Daniel Jacobowitz
2007-10-30 18:29 ` Jim Blandy
2007-10-30 18:41 ` Daniel Jacobowitz
2007-11-01 0:24 ` Jim Blandy [this message]
2007-10-29 23:39 ` Pedro Alves
2007-10-29 23:54 ` Daniel Jacobowitz
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=m33avq3j99.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).