On Sat, Aug 23, 2008 at 4:55 PM, Christopher Sean Morrison
<[EMAIL PROTECTED]> wrote:
> On Aug 22, 2008, at 11:33 AM, Tom Browder wrote:
...
> Thanks, Tom.  I actually worked with one of the cvs2svn devs -- Michael
> Haggerty -- after our migration was completed and we investigated some of
> the issues we ran into.  I don't know if he shared the document with others,
> though, so you're welcome to share it if you like.

Mike is helping with some issues now.

> I talk about some of the fixes we worked out in the UPDATE paragraph under
> "The executable bit" section.  One of which resulted in a change to
> cvs2svn's behavior -- newer versions of cvs2svn should no longer treat
> unvalued auto-prop properties as an indicator to *unset* those properties
> but instead do as svn does and *set* them.  Don't know if that has been
> released into the wild yet.

I'll watch for it.

> There were a couple other bugs we found in the way cvs2svn was dealing with
> old revisions that were both active and in the attic as well as entire
> deletion trees in the attic (which modern cvs doesn't do any more).  Since

That's very interestiing, because in the projects I took over using
CVS that is happening, and I've never seen that.  And we're using a
modern CVS.  Do you have any idea how or why that happens?

> those were easy enough to manually fix (compared to what it would take to
> modify cvs2svn), the changes were just made to the repository prior to the
> run and we left it at that.

Remember how you fixed that?

> The wiki page includes the options file that was used in full.  You should
> be able to copy-paste that into a file of your own.  Let me know if that
> doesn't work for you.

Ok,

>> I would also appreciate a look at your apache option files if
...
> I'd started with the default Apache mime-types file but ultimately didn't
> use it because it caused problems with Tcl files.  It wasn't customized at
> all, though -- it was a default mime-types file that ships with Apache.  As
> for the access protocol setup, we actually get to delegate that all off to
> Sourceforge so they manage the config for providing https/http, etc.

Duh, I should have known that, I'll snoop around SF.

Thanks, Sean.

-Tom

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to