From: Andrew Sayers <andrew-git@pileofstuff.org>
To: Steven Michalske <smichalske@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Sam Vilain <sam@vilain.net>, Stephen Bash <bash@genarts.com>,
Nathan Gray <n8gray@n8gray.org>, Jeff King <peff@peff.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
Dmitry Ivankov <divanorama@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
David Barr <davidbarr@google.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: SVN Branch Description Format
Date: Mon, 19 Mar 2012 01:28:45 +0000 [thread overview]
Message-ID: <4F668BCD.3010306@pileofstuff.org> (raw)
In-Reply-To: <7B2F5CA7-F2C1-483A-9913-B19A14AA9101@gmail.com>
On 18/03/12 23:18, Steven Michalske wrote:
> Consider .SVN_BDF or .SVN.BDF instead of .BDF
>
> I worry about a branch or tag containing a "
> Can subversion contain a "?
>
> Steve
I had a look into valid paths during the week, but hadn't checked quote
marks specifically. Thankfully it seems to work:
mkdir test_dir
cd test_dir
svnadmin create repo
mkdir checkout
svn checkout file://$(pwd)/repo/ checkout/
cd checkout/
mkdir '"'
svn ci -m 'Created directory "'
I'll add this to the test suite :)
Of course, it wouldn't do for SVN to make things that simple. [1] seems
to be the official definition of what a valid path looks like, and I've
skipped over some important requirements in the spec. Most importantly,
redundant '/'s are allowed at the end of a path, and multiple '/'s are
collapsed down to one in SVN, so it seems prudent to import that little
eccentricity into this format.
I could be persuaded about making '.svn-bdf' the recommended extension,
but I'd also be happy to go with a more TLA-friendly name for the whole
thing. "SVN Branch Format" would lend itself neatly to a three-letter
extension (.sbf) that doesn't appear in Wikipedia's list of file
formats[2], although it still encourages the RAS syndrome[3] I've
repeatedly stumbled over while writing the spec. "SVN Branching
Language" might work, and unlike "BDF" or "SBF", "SBL" doesn't sound at
all like "PDF" when mumbled indistinctly. Alternative suggestions are
welcome, with the obvious proviso that this is largely subjective and
I'm going to pick whatever sounds best to my ear :)
I'm approaching a natural break in defining the format, so I'll paste a
new version next week. After that I'll probably pause the format and
work on the SVN exporter for a bit, so I'll have a structure to continue
building the tests and reference implementation against.
- Andrew
[1]http://subversion.apache.org/docs/api/latest/group__svn__fs__directories.html#details
[2]http://en.wikipedia.org/wiki/List_of_file_formats
[3]http://en.wikipedia.org/wiki/RAS_syndrome
next prev parent reply other threads:[~2012-03-19 1:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 10:59 SVN Branch Description Format Andrew Sayers
2012-03-18 23:18 ` Steven Michalske
2012-03-19 1:28 ` Andrew Sayers [this message]
2012-03-19 1:28 ` Licensing a file format (was Re: SVN Branch Description Format) Andrew Sayers
2012-03-19 1:34 ` Jonathan Nieder
2012-03-19 20:31 ` Andrew Sayers
2012-03-20 22:59 ` Jeff King
2012-03-23 0:08 ` SVN Branching Language " Andrew Sayers
2012-03-30 4:06 ` SVN Branch Description Format Ramkumar Ramachandra
2012-03-31 1:27 ` Andrew Sayers
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=4F668BCD.3010306@pileofstuff.org \
--to=andrew-git@pileofstuff.org \
--cc=artagnon@gmail.com \
--cc=bash@genarts.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=n8gray@n8gray.org \
--cc=peff@peff.net \
--cc=sam@vilain.net \
--cc=smichalske@gmail.com \
--cc=srabbelier@gmail.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).