Re: Reorganizing seahorse source code

[Stef Walter <stef-list memberwebs com>]

That works for a blank SVN repository. However we want to maintain
history and our previous change sets, and therefore that new-svn-repos
script doesn't work for us. We need to get a human involved, which so
far hasn't happened. :(

Stef

Adam Schreiber wrote:
> In the process of composing an email to d-d-l concerning our split, I
> remembered we can create our own new modules because we have svn
> accounts.  I looked for some documentation and found
> http://live.gnome.org/NewSVNRepos.  The svn dump part looks like only
> if you're migrating from non-GNOME svn.  We should be able to just
> copy the repository you just created in our module to a new
> seahorse-plugins module.
> 
> We still have to wait on the bugzilla module, but we can at least take
> one step forward.
> 
> Cheers,
> 
> Adam
> 
> On Thu, Apr 17, 2008 at 9:37 PM, Stef Walter <stef-list memberwebs com> wrote:
>>> On Wed, Apr 16, 2008 at 8:47 PM, Stef Walter <stef-list memberwebs com> wrote:
>>  >  I was thinking about something along these lines:
>>  >
>>  >  /tags
>>  >  /branches
>>  >  /trunk
>>  >  /plugins
>>  >    /branches
>>  >    /tags
>>  >    /trunk
>>  >
>>  >  What does everyone think about this plan?
>>
>>  This is now done, both seahorse and seahorse-plugins build and I've
>>  tested it roughly. seahorse-plugins depends on seahorse.
>>
>>  I haven't touched the docs, so that needs some help. I also put in a
>>  request for a bugzilla component.
>>
>>
>>
>>  Cheers,
>>  Stef Walter
>>
>>  _______________________________________________
>>  Seahorse-list mailing list
>>  Seahorse-list gnome org
>>  http://mail.gnome.org/mailman/listinfo/seahorse-list
>>
>