RE: [Axiom-developer] GIT

[Page, Bill]

Gaby,

Since Tim has agreed to what I proposed below and no one
else has disagreed, I would like to plan for this but I
would appreciate your opinion first on how best to do it
without screwing up the SVN repository to badly. Specfically
what we would be trying to do is to replace the existing
/trunk on SourceForge with one derived via Tailor from Tim's
new axiom--silver--1 repository. And to set up a cronjob on
axiom-developer.org to automatically update it each night.

One way to do this would be to first of all delete /trunk
from the repository and rebuild it from the current contents
of axiom--silver--1, but given the little I understand about
how SVN works, I am concerned that using svnadmin to delete
/trunk might have serious consequences for any branch cloned
from /trunk (such as build-improvements). Am I wrong about
that? Is deleteing and re-creating /trunk a safe and sensible
thing to do?

I suppose a safer (but more complex) thing to do would be
to try to compute a changeset that would modify /trunk in
just the right way to make it's current state (but not it's
history!) the same as axiom--silver--1. I could probably do
that by creating a completely separate /trunk2 and then
appropriately diff /trunk and /trunk2 - though I will have
to learn a little more about SVN to do this properly, I
think.

Anyway, your help and suggestions would be appreciated. And
of course anyone else who has some experience with SVN.

Regards,
Bill Page.


On Wednesday, October 25, 2006 10:24 AM Tim Daly wrote:
> 
> > > 
> > > >   tla get axiom--silver--1
> > > ...
> > > I hope it is not too hard for you to convince "tailor" to move
> > > the patches from Tim to SourceForge.
> > > ...
> > 
> Bill Page wrote:
> > If everyone agrees (and especially, Tim Daly agrees) then I would
> > delete the current SourceForge SVN /trunk and replace it with a
> > copy of axiom--silver--1 that is automatically maintained in sync
> > by running Tailor every night, like we currently do between
> > SourceForge and Google and between the build-improvement branch
> > and it's experimental Mercurial and Darcs mirrors. (Actually
> > SourceForge->Google uses the SVN-specific 'svk smerge' command
> > but the result is the same as Tailor between different 
> repositories.)
> > 
> > This would mean that when Tim commits changesets to 
> > axiom--silver--1, SourceForge SVN /trunk would automatically
> > receive the same changes. It would be possible to check out from
> > either axiom--silver--1 or SourceForge SVN /trunk and get the
> > same source code.
> 
> seems reasonable to me.
> 
> t
>