ah, good point. Let's stick to getting this from SVN.
On May 21, 2007, at 1:58 AM, [EMAIL PROTECTED] wrote: > I was thinking a revision history inside the file. I think this technique is used for historical purposes only (from back in the days when getting a log of changes was difficult). I prefer to use the revision control system to get this data. Like databases it makes sense to put data in one place only. When you add this to the file itself you get into having the history in multiple places and it's bound to get out of sync. I vote for putting it in subversion only. Currently, you can get this historical data by just running "svn log": $ svn log Page.py ------------------------------------------------------------------------ r629 | [EMAIL PROTECTED] | 2007-01-13 22:33:45 -0800 (Sat, 13 Jan 2007) | 1 line fixed file encoding problem ------------------------------------------------------------------------ r627 | [EMAIL PROTECTED] | 2007-01-13 22:25:00 -0800 (Sat, 13 Jan 2007) | 1 line misc. tweaks ------------------------------------------------------------------------ r544 | [EMAIL PROTECTED] | 2006-12-13 18:59:33 -0800 (Wed, 13 Dec 2006) | 1 line copied files from trunk to sapling branch. ------------------------------------------------------------------------ r463 | [EMAIL PROTECTED] | 2006-08-25 00:41:37 -0700 (Fri, 25 Aug 2006) | 2 lines dont ever print anything ... $ _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev _______________________________________________ Sycamore-Dev mailing list [EMAIL PROTECTED] http://www.projectsycamore.org/ https://tools.cernio.com/mailman/listinfo/sycamore-dev
