Hi, Alan,

I happened to notice (using gitk to view my local "git svn" clone of the plplot 
repo) the difference that this svn command shows...

svn diff -x -u \
https://plplot.svn.sourceforge.net/svnroot/plplot/tr...@11241 \
https://plplot.svn.sourceforge.net/svnroot/plplot/tags/v5_...@11242

It's not about the properties list so much as it is about some colons that svn 
thinks were deleted.  You'll notice that examples/tcl/x24 was not in my patch 
but does show up in the output of the above svn diff command.  Subversion seems 
to have removed the colon from that file in r11447 (svn diff -c11447).  Weird.  
Maybe it's a difference between old/new version of subversion?

While we're on the topic of keywords, other files that might need to have 
svn:keywords added (or "Id" added to svn:keywords)...

examples/ada/x06a.adb
examples/ada/x07a.adb
examples/ada/xthick06a.adb
examples/ada/xthick07a.adb
examples/python/xw20.py:
examples/python/xw21.py:
examples/python/xw25.py:

These files might have problems (examples/tcl/x25 for sure, $Id:" doesn't seen 
to get expanded)...

examples/d/x04d.d
examples/d/x05d.d
examples/d/x16d.d
examples/d/x20d.d
examples/d/x21d.d
examples/d/x22d.d
examples/d/x26d.d
examples/d/x28d.d
examples/d/x31d.d
examples/tcl/x25

Dave

On Jan 10, 2011, at 1:32 PM, Alan W. Irwin wrote:

> On 2011-01-10 10:09-0800 David MacMahon wrote:
> 
>> 
>> This patch adds the Id keyword changes that were presumably
>> inadvertently committed during the creation of the v5_9_7 tag rather
>> than on trunk.
>> ---
>> examples/f95/x26f.f90 |    2 +-
>> examples/f95/x27f.f90 |    2 +-
>> examples/tcl/x23      |    2 +-
>> examples/tcl/x28      |    2 +-
>> examples/tcl/x29      |    2 +-
>> 5 files changed, 5 insertions(+), 5 deletions(-)
> 
> I am not sure the problem you are trying to correct here is real.  For
> example, I looked at the proplist of examples/f95/*.f90, and they were
> all consistent.  Also the x26f.f90 Id is consistent with the last
> commit for that file on svn/trunk.
> 
> To give you more detail on that summary, here are the properties for
> those files.  (I have used the first example here, but they are all
> the same).
> 
> Properties on 'examples/f95/x01f.f90':
>  svn:keywords
>    Author Date Id Revision
>  svn:eol-style
>    native
> 
> With these properties, then svn will automatically apply the correct
> Id at the time of the last commit.  Here is the result for x26f.f90.
> 
> !  $Id: x26f.f90 8651 2008-08-14 14:23:28Z andrewross $
> 
> Here is what svn log shows for that file.
> 
> ------------------------------------------------------------------------
> r8651 | andrewross | 2008-08-14 07:23:28 -0700 (Thu, 14 Aug 2008) | 4
> lines
> 
> Add f95 versions of examples 24, 25, 26 and 27. Results are consistent with 
> the C versions.
> 
> ------------------------------------------------------------------------
> 
> This all looks fine to me.
> 
> Alan
> __________________________
> Alan W. Irwin
> 
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
> 
> Programming affiliations with the FreeEOS equation-of-state implementation
> for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
> package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
> Linux Links project (loll.sf.net); and the Linux Brochure Project
> (lbproject.sf.net).
> __________________________
> 
> Linux-powered Science
> __________________________


------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl 
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to