[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Mon, 2005-12-05 at 07:20 +1100, Peter Wang wrote:
> On 2005-12-04, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> > On Sun, 2005-12-04 at 15:57 +1100, Peter Wang wrote:
> > >
> > > Yup, thanks. Is there anyone who doesn't like that layout? Otherwise
> > > we'll make it official. Nobody commit to the CVS tree for the `allegro'
> > > and `makedoc' modules anymore. I've tagged the CVS repository with a
> > > `svn_migration_point'.
> > >
> >
> > Should we delete "allegrowww" "allegro_new" from SVN?
>
> I was about to delete allegro_new but backed off. They should probably
> both go.
allegro_new has no actual code changes in it AFAIK, just al_ prefixes.
Maybe should investigate first though..
> > Also, I'd like to rename:
> >
> > allegro/trunk -> allegro/branches/allegro_4_2
>
> Or just allegro/branches/4.2
>
> > allegro/branches/new_api_branch -> allegro/branches/allegro_4_4
>
> This should be 4.3.
>
Yes, of course, 4.3. And I agree, just the version number looks better.
I went ahead and moved both over.
So, from now on, 4.2/4.3 commits should go to:
allegro/branches/4.2
allegro/branches/4.3
If someone already checked out "allegro/trunk" or
"allegro/branches/new_api_branch", simply use svn switch, no need to do
a new checkout, e.g. for new_api_branch, from inside the dir:
svn switch http://svn.bafserv.com/svn/allegro/allegro/branches/4.3
--
Elias Pschernig