On Sun, Nov 13, 2011 at 5:57 PM, Neels J Hofmeyr ne...@elego.de wrote:
On 11/11/2011 11:41 AM, Julian Foad wrote:
Neels J Hofmeyr wrote:
I think there is general agreement (to the degree of common
sense?) that file and dir externals should behave the same
way.
+1 to that.
I would be
Neels J Hofmeyr wrote on Thu, Nov 10, 2011 at 21:34:30 +0100:
It was suggested to extend the svn:externals syntax, adding a flag
that marks externals that should behave differently. By now this
seems to me to be the best way out. What would that look like?
[-rN] [-c] URL@P PATH
-c =
Neels J Hofmeyr wrote:
I think there is general agreement (to the degree of common
sense?) that file and dir externals should behave the same
way.
+1 to that.
I would be fine with keeping current trunk: it changes file
externals' default behavior, so that they are treated like
dir
On 11/10/2011 07:10 PM, C. Michael Pilato wrote:
As a community, we need to decide how we will handle file externals in
general. Their clever implementation invites inconsistency.
I think there is general agreement (to the degree of common sense?) that
file and dir externals should behave
On 11/10/2011 03:34 PM, Neels J Hofmeyr wrote:
It was suggested to extend the svn:externals syntax, adding a flag that
marks externals that should behave differently. By now this seems to me to
be the best way out. What would that look like?
The next change we make to the externals syntax
On 11/10/2011 09:39 PM, C. Michael Pilato wrote:
The next change we make to the externals syntax needs to be to add an
explicit #format = 3 header to it so we can stop trying to deduce the
format the user intended!
now that's cumbersome. a footer would be much nicer. ;)
~Neels
6 matches
Mail list logo
