Am 28.04.2010 08:50, schrieb hend...@topoi.pooq.com: > On Wed, Apr 28, 2010 at 12:36:59PM +0200, Thomas Moschny wrote: >> Am Sun, 18 Apr 2010 20:49:37 +0200 >> schrieb Thomas Keller <m...@thomaskeller.biz>: >> >>> Secondly, I'd actively deprecate any branch name which does not match >>> the following regular expression, i.e. by throwing a warning when a >>> branch cert which a different value is created: >>> >>> ^([\w\d]+([-][\w\d]+)*)(\.[\w\d]+([-][\w\d]+)*)*$ >> >> Sounds good to me, but maybe we have to ask our users, whether that'd >> be ok for them. And we should still allow them to use other branch names >> if they wish so (because technically, there's no need for such a >> restriction). >> >> "mtn ls branches | grep -v -E '^(\w+(-\w+)*)(\.\w+(-\w+)*)*$'" shows only >> one branch that doesn't match in my local copy of the monotone db >> (prjek.net:tester). > > And what would you do with that branch if this were to become a > restriction?
Well, we could still handle branches like this, but we'd enforce the
usage of url encoding, i.e. if a branch name looks like this
-foo*,bar
we would be able to handle it when it is given so:
%2Dfoo%2Cbar%2A
And to avoid that the user would have to encode that by hand, we'd make
the "compatibility" arguments and options BRANCH_PATTERN [--exclude=...]
to convert the given value to the internal, url-escaped version.
Thomas.
--
GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
