Jeremias Maerki wrote:
How will we maintain the website after the copy? Change in trunk then
copy over to maint branch each time something is changed? Or can we
Yes, I'm not sure if automatic merging would work and I don't think
there will be a lot of changes.
Christian
Peter B. West wrote:
> Victor Mote wrote:
> > Christian Geisert wrote:
> >
> >
> >>for the documentation for the maintenance release I think the
> >>best thing is to copy src/documentation over from trunk and then
> >>add a simple to build.xml
> >>Comments?
> >
> >
> > I had a thought left over f
On Thu, 2002-11-28 at 17:33, Christian Geisert wrote:
> Hi,
>
> for the documentation for the maintenance release I think the
> best thing is to copy src/documentation over from trunk and then
> add a simple to build.xml
> Comments?
>
> The track.png in status.html needs a update. How is it done
Victor Mote wrote:
Christian Geisert wrote:
for the documentation for the maintenance release I think the
best thing is to copy src/documentation over from trunk and then
add a simple to build.xml
Comments?
I had a thought left over from our discussion of branching a few weeks ago
that migh
Christian Geisert wrote:
> for the documentation for the maintenance release I think the
> best thing is to copy src/documentation over from trunk and then
> add a simple to build.xml
> Comments?
I had a thought left over from our discussion of branching a few weeks ago
that might help here. I c
How will we maintain the website after the copy? Change in trunk then
copy over to maint branch each time something is changed? Or can we
somehow keep both documentation parts separate in their branches and
copy the stuff together when the website needs an update?
On 28.11.2002 17:33:51 Christian
Hi,
for the documentation for the maintenance release I think the
best thing is to copy src/documentation over from trunk and then
add a simple to build.xml
Comments?
The track.png in status.html needs a update. How is it done?
Christian
--
