With tdbc and itcl now bundled, developers of core Tcl are going to
encounter their bugs more frequently, and with luck discover and
contribute fixes.  That's great!

However, it would be most helpful to me and I believe to the upstream
developers of these packages to contribute those fixes upstream, and
not by committing fixes to the directories in our repository that import
upstream releases.

I really don't want to be in the position as release manager of deciding
what local patches do and do not go into our releases, and whether
having our own customizations demands a new version number or package
name or other relabeling.  I just want to take what upstream gives and
send it back out again.

One way to structure your sandbox so that you won't mistakenly commit
patches to the Tcl repos is to checkout the "tcl-only" module and then
fill the tcl/pkgs directory of your sandbox from the upstream sources.
Then you can arrange to be working off the "HEAD" of everything.

-- 
| Don Porter          Mathematical and Computational Sciences Division |
| donald.porter@[...].gov             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Tcl-Core mailing list
Tcl-Core@[...].net
https://lists.sourceforge.net/lists/listinfo/tcl-core