On Thu, Oct 19, 2017 at 11:58 PM, Johan Corveleyn wrote:
> On Thu, Oct 19, 2017 at 10:04 PM, Johan Corveleyn wrote:
>> On Thu, Oct 5, 2017 at 11:42 PM, Branko Čibej wrote:
>>> On 05.10.2017 22:36, Johan Corveleyn wrote:
On Thu, Oct 5, 2017 at 12:30 PM, Daniel Shahaf
wrote:
> Devi
On Thu, Oct 19, 2017 at 10:04 PM, Johan Corveleyn wrote:
> On Thu, Oct 5, 2017 at 11:42 PM, Branko Čibej wrote:
>> On 05.10.2017 22:36, Johan Corveleyn wrote:
>>> On Thu, Oct 5, 2017 at 12:30 PM, Daniel Shahaf
>>> wrote:
Devil's advocate hat on, and in light of Brane's sibling reply, let m
On Thu, Oct 5, 2017 at 11:42 PM, Branko Čibej wrote:
> On 05.10.2017 22:36, Johan Corveleyn wrote:
>> On Thu, Oct 5, 2017 at 12:30 PM, Daniel Shahaf
>> wrote:
>>> Devil's advocate hat on, and in light of Brane's sibling reply, let me
>>> describe how an svnmucc workflow might work.
>> Thanks, bu
On 05.10.2017 22:36, Johan Corveleyn wrote:
> On Thu, Oct 5, 2017 at 12:30 PM, Daniel Shahaf
> wrote:
>> Devil's advocate hat on, and in light of Brane's sibling reply, let me
>> describe how an svnmucc workflow might work.
> Thanks, but I prefer the merge workflow. It seems more natural to me,
>
On Thu, Oct 5, 2017 at 12:30 PM, Daniel Shahaf wrote:
> Devil's advocate hat on, and in light of Brane's sibling reply, let me
> describe how an svnmucc workflow might work.
Thanks, but I prefer the merge workflow. It seems more natural to me,
and I think it's more likely to be used by other svn
Devil's advocate hat on, and in light of Brane's sibling reply, let me
describe how an svnmucc workflow might work.
Johan Corveleyn wrote on Thu, 05 Oct 2017 01:13 +0200:
> - Maybe we'll have some change on staging that we don't want to merge
> to publish (I mean, something like showing a differen
On 05.10.2017 01:13, Johan Corveleyn wrote:
> On Wed, Oct 4, 2017 at 1:21 PM, Daniel Shahaf wrote:
>> Bert Huijben wrote on Wed, 04 Oct 2017 11:07 +0200:
-Original Message-
From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
I'd like to understand the topology / flow o
On Wed, Oct 4, 2017 at 1:21 PM, Daniel Shahaf wrote:
> Bert Huijben wrote on Wed, 04 Oct 2017 11:07 +0200:
>> > -Original Message-
>> > From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
>> >
>> > I'd like to understand the topology / flow of changes: what ensures that
>> > changes made
Bert Huijben wrote on Wed, 04 Oct 2017 11:07 +0200:
> > -Original Message-
> > From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> >
> > I'd like to understand the topology / flow of changes: what ensures that
> > changes made directly to publish are not reverted by a subsequent
> > pro
> -Original Message-
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Sent: woensdag 4 oktober 2017 02:05
> To: dev@subversion.apache.org
> Subject: Re: Workflow for editing the subversion website
>
> Johan Corveleyn wrote on Tue, 03 Oct 2017 23:32 +0200:
&
Johan Corveleyn wrote on Tue, 03 Oct 2017 23:32 +0200:
> The recent work on our quick-start.html page by Pavel Lyalyakin
> prompted some thinking about how to better organize our site editing.
> Pavel asked about lightweight branching and Daniel suggested to copy
> site/publish to site/staging and
On 03.10.2017 23:32, Johan Corveleyn wrote:
> The recent work on our quick-start.html page by Pavel Lyalyakin
> prompted some thinking about how to better organize our site editing.
> Pavel asked about lightweight branching and Daniel suggested to copy
> site/publish to site/staging and having it s
12 matches
Mail list logo
