incubator-heraldry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Recordon, David" <>
Subject RE: svn commit: r526301 - /incubator/heraldry/idp/pip/trunk/vendor/plugins/security_extensions/
Date Sat, 07 Apr 2007 17:13:47 GMT
I'm happy to try out Piston then, Dan do you have any thoughts on it?
( also
seems quite reasonable to use and it looks like Piston is basically
doing the same thing though a bit more Rails specific around plugin
version numbers versus just SVN commit numbers.

So I'm thinking that we try out Piston first unless Dan knows something
bad about it.


-----Original Message-----
From: Matt Pelletier [] 
Sent: Friday, April 06, 2007 10:10 PM
Subject: Re: svn commit: r526301 -

Piston uses svn's property setters/getters (which is what svn:externals
uses) to know which rev of the foreign repository you currently have.
When you want to "piston update" it will find the latest, pull it down,
diff and merge with your local copy.

I've switched to it for most projects where I used to use externals.  
In some cases I prefer it because I don't want a Rails app to be
dependent upon changes in its plugins. In most cases I prefer it because
it's just more convenient.


On Apr 6, 2007, at 7:16 PM, Recordon, David wrote:

> Hey Elliot,
> Never played with piston before, though Paul is right that we really 
> should be moving to using externals.  I'd be happy to try piston.  Any

> other thoughts about piston versus straight up svn externals?
> --David
> -----Original Message-----
> From: Elliott Cable [] On Behalf Of 
> elliott cable
> Sent: Friday, April 06, 2007 3:59 PM
> To:
> Subject: Re: svn commit: r526301 -
> /incubator/heraldry/idp/pip/trunk/vendor/plugins/security_extensions/
> Considered using piston? Not exactly sure what you're doing, but I saw

> rails references and vendor branches and SVN in the same message, so I

> thought I'd tip in d-:
> ---------------------------------------------------------
>       elliott cable       _     _      +1.202.370.7968
>                          ( \---/ )
>     ) . . (
> ___________________,--._(___Y___)_,--.___________________
>                     `--'           `--'
> THIS MESSAGE (and any attached materials) IS INTENDED ONLY FOR THE USE

> DISCLOSURE UNDER APPLICABLE LAW.  If you, the reader of this message, 
> are not the intended recipient or the agent responsible for delivering

> the message to the intended recipient, you are hereby notified that 
> any dissemination, distribution, or copying of this communication is 
> strictly prohibited.  If you have received this communication in 
> error, please notify me immediately by replying to this message and 
> deleting all traces of it from your computer.  Thank you.
> _________________________________________________________
> On Apr 6, 2007, at 2:49 PM, Paul Querna wrote:
>> wrote:
>>> Author: recordond
>>> Date: Fri Apr  6 15:30:33 2007
>>> New Revision: 526301
>>> URL:
>>> Log:
>>> Remove current security_extensions plugin to be replaced by latest 
>>> version in next commit.
>>> Removed:
>>>     incubator/heraldry/idp/pip/trunk/vendor/plugins/
>>> security_extensions/
>> Rather than deleting directories (and hiding some history from easy 
>> browsing), doesn't it make sense to treat external code like a vendor

>> branch?
>> The svn book has details on how to do this:

Matt Pelletier -- EastMedia -- The Mongrel Book -- OpenID, Identity 2.0

View raw message