On 4/2/06, Jens Vagelpohl <[EMAIL PROTECTED]> wrote:
> Thanks Rob! I hope Lennart and Yvo will take a look this weekend or
> Monday.
I checked out the current 1.6 and ran some of our tests with it and
has used it today, and it seems to work fine.
--
Lennart Regebro, Nuxeo http://www.nuxeo.com
Hi Florent!
Florent Guillaume wrote:
Jens Vagelpohl wrote:
On 2 Apr 2006, at 09:34, Rob Miller wrote:
it's in now, r66291.
and i've also committed the .delete file support implementation,
again on the 1.6 branch. if there are no complaints, i'll merge to
2.0 and trunk on monday.
Thanks R
Jens Vagelpohl wrote:
On 2 Apr 2006, at 09:34, Rob Miller wrote:
it's in now, r66291.
and i've also committed the .delete file support implementation, again
on the 1.6 branch. if there are no complaints, i'll merge to 2.0 and
trunk on monday.
Thanks Rob! I hope Lennart and Yvo will take a l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2 Apr 2006, at 09:34, Rob Miller wrote:
Rob Miller wrote:
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i've committed this on the 1.6 branch.
Rob, I didn't get any commit message email and a quick look at
svn.zope.
Rob Miller wrote:
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i've committed this on the 1.6 branch.
Rob, I didn't get any commit message email and a quick look at
svn.zope.org doesn't show any recent changes on the 1.6 branch in the
last 3 weeks?
that's what happ
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i've committed this on the 1.6 branch.
Rob, I didn't get any commit message email and a quick look at
svn.zope.org doesn't show any recent changes on the 1.6 branch in the
last 3 weeks?
that's what happens when you try to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i've committed this on the 1.6 branch.
Rob, I didn't get any commit message email and a quick look at
svn.zope.org doesn't show any recent changes on the 1.6 branch in the
last 3 weeks?
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4
Lennart Regebro wrote:
On 3/31/06, Rob Miller <[EMAIL PROTECTED]> wrote:
i've committed this on the 1.6 branch. this is a pretty significant
change in behaviour. before, a reimport would delete EVERYTHING that
was not explicitly protected by the ".preserve" file of the currently
active profile
On 3/31/06, Rob Miller <[EMAIL PROTECTED]> wrote:
> i've committed this on the 1.6 branch. this is a pretty significant
> change in behaviour. before, a reimport would delete EVERYTHING that
> was not explicitly protected by the ".preserve" file of the currently
> active profile. now, content wi
Rob Miller wrote:
Jens Vagelpohl wrote:
There's a bug filed already: http://www.zope.org/Collectors/CMF/404
I have asked Tres to look at it since he did most of the
content-related stuff but haven't heard from him. If you know a
solution, by all means, go for it.
okay, i've got an implement
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29 Mar 2006, at 11:09, Rob Miller wrote:
this changes some unit test results, and i need to write another test
or two, but it's time for bed. if this seems a reasonable approach
i'll finish it up and commit the changes on
Hi Rob!
Rob Miller wrote:
yuppie wrote:
Rob Miller wrote:
- allow extension profiles to specify which of the base profile's
import steps they depend on, so that only these can be run, instead
of the current situation where, AFAICT, you have to either run them
all or manually examine the pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29 Mar 2006, at 11:09, Rob Miller wrote:
this changes some unit test results, and i need to write another
test or two, but it's time for bed. if this seems a reasonable
approach i'll finish it up and commit the changes on trunk and 1.6
bran
yuppie wrote:
Hi Rob!
Rob Miller wrote:
- allow extension profiles to specify which of the base profile's
import steps they depend on, so that only these can be run, instead of
the current situation where, AFAICT, you have to either run them all
or manually examine the profile and select the
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29 Mar 2006, at 08:25, Rob Miller wrote:
my base profile is a default Plone site, which does a bunch of
configuration and adds a few pieces of content using the "structure"
folder mechanism that is supported by CMFCore's
S
Hi Rob!
Rob Miller wrote:
maybe i'm missing something fundamental, but i'm having trouble figuring
out how i'm supposed to apply extension profiles to my site. the
intended mechanism is clear enough; set the active configuration to be
the desired profile and then execute runAllImportSteps on
16 matches
Mail list logo
