Re: [Tcllib-devel] Heads Up! Transition! CVS/SF --> Fossil/core.tcl.tk

[Johann O. <joh...@go...>]

Hi Roy,

thank you very much for your effort.

I introduced quite a lot of code changes at that time (Sept. 2009) for a better ttk support.
The branch was called 1.9.1.

Later on we (Harald and me) found out, that not all changes are backward compatible on all platforms and would probably cause existing programs to fail.

The timeline shows that 2 branches were maintained in parallel for a while, whereas the intention of the 1.9.1 branch was somehow more "experimental".

For the migration to fossil you can simply forget the 1.9.1 branch and use the source maintained by Harald, tagged as 1.9.6.


Thanks all,
  Johann




The branch which was committed into the cvs  1.9.1
On 10.12.2012, at 18:41, Roy Keene <rk...@rk...> wrote:

> Andreas,
> 
> 	Setting the main branch to "BWidget" isn't a problem.
> 
> Harald,
> 
> 	Looking at the timeline here:
> 		http://rkeene.org/projects/tcl/TESTING/bwidget.fossil/timeline?n=2000
> 
> Can you provide any insight into why the commit on 10-AUG-2009 is based on 
> the state of the repository 09-SEP-2009 ?
> 
> Is that a legitimate branch that happened in August and didn't make its 
> way into trunk into September and the branchpoint is just wrong ?
> 
> Thanks,
> 	Roy Keene
> 
> On Mon, 10 Dec 2012, Andreas Kupries wrote:
> 
>> On Sun, Dec 9, 2012 at 11:48 PM, Harald Oehlmann
>> <har...@el...> wrote:
>>> Andreas,
>>> 
>>> thank you for the work !
>> 
>> You are welcome.
>> 
>>> 
>>> Am 07.12.2012 19:04, schrieb Andreas Kupries:
>>>> The only exception is the BWidget CVS which contains a timewarp Roy
>>>> Keene (our conversion guy) has to straighten out first before we can
>>>> put the resulting Fossil up on core also. That should happen sometime
>>>> next week.
>>> 
>>> Within BWidget, the main branch is currently not "trunk" but tag
>>> "BWidget". I am not shure, if we should change this ?
>> 
>> IMHO yes. Roy ?
>> 
>>>> Side note on that: The repositories are in what fossil calls a
>>>> login-group. Logging into one of them will log you into all, and if
>>>> you change your password in one of them it will change in all the
>>>> others also.
>>> 
>>> Is it in a login group with the tcl repository or do all tcllib
>>> repositories form an own login group ?
>> 
>> They are their own login group.
>> 
>>> 
>>> E.g. do people which already have commit access on core.tcl.tk/tcl
>>> require a second login
>> 
>> Yes.
>> 
>>> or is this automatic ? If yes, I apply commit
>>> access for "oehhar".
>> 
>> Separate mail will be forthcoming.
>> 
>> --
>> Andreas Kupries
>> Senior Tcl Developer
>> Code to Cloud: Smarter, Safer, Faster?
>> P: 778.786.1122
>> F: 778.786.1133
>> and...@ac...
>> http://www.activestate.com
>> Learn about Stackato for Private PaaS: http://www.activestate.com/stackato
>> 
>> Tcl'2013, Sep 23-27, New Orleans, LA, USA.
>> 
> 
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Tcllib-devel mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcllib-devel