On Sat, Oct 29, 2011 at 11:27 PM, Nico Kadel-Garcia wrote:
>>
>> Yes, but the packaged linux versions pretty much just come up working
>> under http(s) with a appropriate line or two added to the packaged
>> configuration to point to the repository location, and once a network
>> server works, sv
On Sun, Oct 30, 2011 at 12:26 PM, Les Mikesell wrote:
> On Sat, Oct 29, 2011 at 11:27 PM, Nico Kadel-Garcia wrote:
>>>
>>> Yes, but the packaged linux versions pretty much just come up working
>>> under http(s) with a appropriate line or two added to the packaged
>>> configuration to point to the
At last I've discovered
how to get my first “svn.exe”, “svnadmin.exe”, ..., up and running.
It was as simple as pie [better: trivial], once you knew it.
I'll take good note of
this experience and write it down into my of memories, when retired.
Thank you all. - P.M.
On Sun, Oct 30, 2011 at 1:26 PM, Nico Kadel-Garcia wrote:
>
> An ordinary newbie Subversion administrator *will not be aware* of
> these security issues. Precisely as you've shown, it's considered "not
> our problem" by the Subversion source developers.
It's not that it is not subversion's proble
[Accidentally sent this just to Les: Les, sorry if you get two copies!]
On Sun, Oct 30, 2011 at 3:04 PM, Les Mikesell wrote:
> On Sun, Oct 30, 2011 at 1:26 PM, Nico Kadel-Garcia wrote:
>>
>> An ordinary newbie Subversion administrator *will not be aware* of
>> these security issues. Precisely as
The old directorions for submitting patches say to send them to
"d...@subversion.org", but I'm getting bounces. It's making it kind of
hard to submit the patches be able to build SRPM's for
subversion-1.7.1.
Is there a better address? I've gotten it working with RHEL 5, RHEL 6,
and Fedora 15.
On Sun, Oct 30, 2011 at 03:38:54PM -0400, Nico Kadel-Garcia wrote:
> The old directorions for submitting patches say to send them to
> "d...@subversion.org", but I'm getting bounces. It's making it kind of
> hard to submit the patches be able to build SRPM's for
> subversion-1.7.1.
>
> Is there a b
On Sun, Oct 30, 2011 at 3:56 PM, Stefan Sperling wrote:
> On Sun, Oct 30, 2011 at 03:38:54PM -0400, Nico Kadel-Garcia wrote:
>> The old directorions for submitting patches say to send them to
>> "d...@subversion.org", but I'm getting bounces. It's making it kind of
>> hard to submit the patches be
On Sun, Oct 30, 2011 at 4:41 PM, Nico Kadel-Garcia wrote:
> The "community guide" at
> http://subversion.apache.org/docs/community-guide/general.html gets it
> correct, but I had an old copy stashed. Glad to see it's corrected
> there.
That was an old copy of the *contact*, in my GMail contacts,
Hi Everyone,
I hoping that I can get some help with the theory of cherry-picking merges to a
branch.
I have the "default" subversion layout;
/trunk
/branches
/tags
I have a "release branch"; ^/branches/releases/1.5
I have "^/trunk/filename.txt"
I have just created a release branch, made some
On Mon, Oct 31, 2011 at 10:18 AM, Gavin "Beau" Baumanis <
gavin.bauma...@palcare.com.au> wrote:
> Hi Everyone,
>
> I hoping that I can get some help with the theory of cherry-picking merges
> to a branch.
>
> I have the "default" subversion layout;
> /trunk
> /branches
> /tags
>
> I have a "releas
Hi Daniel,
I am certain that I had tried that previously and it didn't work.
Well the command worked, of course but the results were not what I was
expecting.
Up until recently we did not have a "staged" release strategy.
We did continuous deployment of ALL changes submitted to the repostor
12 matches
Mail list logo
