defaria.com/blogs/Status/archives/week_2005_05_22.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml"$>" />
  11
  12    <title>Status for Andrew DeFaria: May 22, 2005 - May 28, 2005 Archives</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/week_2005_05_15.html" title="May 15, 2005 - May 21, 2005" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2005_05_29.html" title="May 29, 2005 - June  4, 2005" />
  17 </head>
  18 <body class="layout-one-column">
  19    <div id="container">
  20       <div id="container-inner" class="pkg">
  21
  22          <div id="banner">
  23             <div id="banner-inner" class="pkg">
  24                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  25                <h2 id="banner-description">Searchable status reports and work log</h2>
  26             </div>
  27          </div>
  28
  29          <div id="pagebody">
  30             <div id="pagebody-inner" class="pkg">
  31                <div id="alpha">
  32                   <div id="alpha-inner" class="pkg">
  33
  34                      <p class="content-nav">
  35                         <a href="http://defaria.com/blogs/Status/archives/week_2005_05_15.html">&laquo; May 15, 2005 - May 21, 2005</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/week_2005_05_29.html">May 29, 2005 - June  4, 2005 &raquo;</a>
  38                      </p>
  39
  40
  41
  42
  43                      <h2 class="date-header">May 26, 2005</h2>
  44                      <a id="a000364"></a>
  45                      <div class="entry" id="entry-364">
  46                         <h3 class="entry-header">Build notes LW/GD and tst</h3>
  47                         <div class="entry-content">
  48                            <div class="entry-body">
  49                               <ul>
  50   <li>Caught up on build notes for 20050425, 20050519 and 20050525 for LW LOS178</li>
  51
  52   <li>Resolved CR 41</li>
  53
  54   <li>Tagged tst's for LW LOS178</li>
  55
  56   <li>Assisted Adisak with lists for CRs 536 and 584</li>
  57 </ul>
  58
  59                               <p class="entry-footer">
  60                                  <span class="post-footers">Posted by  at  6:09 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000364.html">Permalink</a>
  61
  62
  63                               </p>
  64                            </div>
  65                         </div>
  66                      </div>
  67
  68
  69
  70                      <h2 class="date-header">May 25, 2005</h2>
  71                      <a id="a000363"></a>
  72                      <div class="entry" id="entry-363">
  73                         <h3 class="entry-header">LW & GD builds</h3>
  74                         <div class="entry-content">
  75                            <div class="entry-body">
  76                               <ul>
  77   <li>Incorporated CR 598 which fixes the production build</li>
  78
  79   <li>Tagged LW LOS178 20050525, rebuilt, released</li>
  80
  81   <li>Ported CR 598 to GD</li>
  82
  83   <li>Tagged GD LOS178 20050525, rebuilt, released</li>
  84
  85   <li>Created build_notes for GD 20050428</li>
  86
  87   <li>Associated updating of related CRs</li>
  88 </ul>
  89
  90                               <p class="entry-footer">
  91                                  <span class="post-footers">Posted by  at  6:38 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000363.html">Permalink</a>
  92
  93
  94                               </p>
  95                            </div>
  96                         </div>
  97                      </div>
  98
  99
 100
 101
 102                      <a id="a000362"></a>
 103                      <div class="entry" id="entry-362">
 104                         <h3 class="entry-header">PPC Pdn build Failure/CVS Report bug</h3>
 105                         <div class="entry-content">
 106                            <div class="entry-body">
 107                               <ul>
 108   <li>Was unable to build ppd_pdn due to a bug</li>
 109
 110   <li>Found a bug in cvs_report regarding new directories</li>
 111 </ul>
 112
 113                               <h3>cvs_report bug</h3>
 114
 115 <p>The cvs_report script determines what has changed by using cvs update, just like the old one. But it uses -n to not actually update the area. If it did actually update it then it would have to downdate it (for lack of a better term) for the next night's run. But there is a side effect to not doing the actual update: If there is a new directory the -n will prevent cvs update from looking into what's in the new directory! I did not know this.</p>
 116
 117 <p>This effects CR #570 and possibly others. CR #570 adds a new directory under src/lib/libm called complex with 52 new files. These files did not get included in the list of files to port over.</p>
 118
 119 <p>Additionally cvs_report had an error in a regex such that it was not identifying these new files properly. This has also been fixed.</p>
 120
 121                               <p class="entry-footer">
 122                                  <span class="post-footers">Posted by  at  6:30 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000362.html">Permalink</a>
 123
 124
 125                               </p>
 126                            </div>
 127                         </div>
 128                      </div>
 129
 130
 131
 132                      <h2 class="date-header">May 23, 2005</h2>
 133                      <a id="a000361"></a>
 134                      <div class="entry" id="entry-361">
 135                         <h3 class="entry-header">files4cr</h3>
 136                         <div class="entry-content">
 137                            <div class="entry-body">
 138                               <p>Both files4ecr and files4cr will suffer this same problem. Let's say we had an E/CR with 10 files modified.  If at some later time one of these 10 files is changed, or another file modified with this same E/CR number it will show up in the CVS Report as only that one file modified since the CVS Report goes from some base tag to some other tag (e.g. head). The difference between those tags is only that one file - rightfully so.</p>
 139
 140 <p>However both files4ecr and files4cr work off of the E/CR number identifying <b>all</b> files associated with that E/CR number, irrespective of any other tags that they might have. So the files4cr in the above scenario would pick up all 11 files!</p>
 141
 142 <p>Now according to CVS a commit command should not commit files that have not been modified. The question is what does CVS use to determine that a file has been modified? Contents modified or just say date/timestamp modified? It appears that it's content modified</p>
 143
 144 <p>Still this makes files4[e]cr not very efficient. For example, CR #542 consists of ~3200 files that were modified. Since the last dev build 17 more files were modified. But files4cr picks up ~3200 files! If we are to transfer these over to GD then commit that seems like a large waste of effort</p>
 145
 146                               <p class="entry-footer">
 147                                  <span class="post-footers">Posted by  at  2:10 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000361.html">Permalink</a>
 148
 149
 150                               </p>
 151                            </div>
 152                         </div>
 153                      </div>
 154
 155                   </div>
 156                </div>
 157             </div>
 158          </div>
 159       </div>
 160    </div>
 161 </body>
 162 </html>