On Thu, Mar 1, 2012 at 6:17 PM, Hervé BOUTEMY wrote:
> if you look at committer environment [1], you'll see that there is a
> subversion configuration with precisely svn-eol-style.txt
> That's the default properties developer's svn client sets on files: here is
> the
> way properties are defined
if you look at committer environment [1], you'll see that there is a
subversion configuration with precisely svn-eol-style.txt
That's the default properties developer's svn client sets on files: here is the
way properties are defined when adding a file to svn, even if SCM API doesn't
tell anythi
On Wed, Feb 29, 2012 at 9:46 PM, Chris Graham wrote:
> I'm confused.
>
> HTML is a text file, so what does it's EOL style matter?
What can I tell you? I got bit in the ankle by a CRLF at an early age
and I try to stomp on them whenever I can ever since.
>
> But you address your other question,
I'm confused.
HTML is a text file, so what does it's EOL style matter?
But you address your other question, the only way that I know is to do a
propset of svn:eol-style.
And I am not aware that the SCM API has the facility to do this.
I'm pretty sure (as that's where I've been poking around lat
On the subject of newlines: personally, I think that Windows newlines
in HTML files are evil. However, if that is an exotic belief on my
part, I don't mind changing the code to normalize to native. It would
be good to know what the svn eol-style is, but I don't see how do do
that through scm.
I forgot to check in my last set of changes, including most of
usage.apt.vm. I just checked it in.
I didn't name that class 'Abstract' because, well, I couldn't think of
any 'abstract' methods to include in it :-)
On Wed, Feb 29, 2012 at 5:49 PM, Hervé BOUTEMY wrote:
> sorry, I can't find which
I am a little lost - and sitting in a car. the doc I refer to is the
apt doc in svn. did you add comments to the source there? I will up &
read when I get home.
On Feb 29, 2012, at 5:49 PM, "Hervé BOUTEMY" wrote:
> sorry, I can't find which doc you're referring to: can you point me to it,
> ple
sorry, I can't find which doc you're referring to: can you point me to it,
please?
did you see the comments I added to actual sources? Are they accurate, or did
I miss something?
Regards,
Hervé
Le mercredi 29 février 2012 17:43:03 Benson Margulies a écrit :
> On Wed, Feb 29, 2012 at 5:03 PM,
On Wed, Feb 29, 2012 at 5:03 PM, Hervé BOUTEMY wrote:
> wouldn't be following lifecycle more appropriate?
> svnpubsub:prepare: do an svn checkout
> site:stage -DstagingDirectory = svn checkout dir
> svnpusub:publish: do the svn checkins
I think that this is essentially one of the two opt
wouldn't be following lifecycle more appropriate?
svnpubsub:prepare: do an svn checkout
site:stage -DstagingDirectory = svn checkout dir
svnpusub:publish: do the svn checkins
then using "mvn site svnpubsub" would do the job
and the site build would be standard, whatever steps are invol
that would be a disaster with svn. it is a wagon so has no cross-file
state. it is already really slow with git. else we could use kk 's
wagon-svn
On Feb 26, 2012, at 2:42 PM, Stephen Connolly
wrote:
> Have you looked at how Katherine H's gitsite works... Seems we basically want
> the same
>
>
Have you looked at how Katherine H's gitsite works... Seems we basically want
the same
Sent from my iPhone
On 25 Feb 2012, at 18:52, Benson Margulies wrote:
> On Sat, Feb 25, 2012 at 1:45 PM, Hervé BOUTEMY wrote:
>> why not consider it as a deploy protocol?
>> like scp, file, webdav: svnpubsu
On Sat, Feb 25, 2012 at 1:45 PM, Hervé BOUTEMY wrote:
> why not consider it as a deploy protocol?
> like scp, file, webdav: svnpubsub
That only handles the last piece.
Here's the lifecycle:
svnpubsub:prepare: do an svn checkout
site:site
site:stage -DstagingDirectory = svn checkout
why not consider it as a deploy protocol?
like scp, file, webdav: svnpubsub
then the existing site-deploy phase of site lifecycle is sufficient
Le samedi 25 février 2012 11:58:36 Benson Margulies a écrit :
> To make the svnpubsub thing easier to use, I'd like to declare a
> customer lifecycle for
To make the svnpubsub thing easier to use, I'd like to declare a
customer lifecycle for it. Perhaps I need to break for lunch, but can
I do that without a packaging? I just want to let someone type
mvn svnpubsub
and watch the fun.
--
15 matches
Mail list logo
