On 28/05/2009, Rahul Akolkar <[email protected]> wrote: > On Thu, May 28, 2009 at 6:47 AM, sebb <[email protected]> wrote: > > On 28/05/2009, sebb <[email protected]> wrote: > >> On 28/05/2009, Henri Yandell <[email protected]> wrote: > >> > On Wed, May 27, 2009 at 5:57 AM, Emmanuel Bourg <[email protected]> > wrote: > >> > > >> > > Could everyone look at their projects and fix the files please? > >> > > >> > > >> > Just as a note - there's no reason why someone can't do all of them if > >> > they want. > >> > >> > >> BTW, the DOAPs are referenced from > >> > >> > http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml > >> > >> > >> > Should be a simple regex. > >> > >> > >> Not totally simple, as revision only needs to be converted if it is > >> the container. > >> > > > > And as I found out just now, it's very easy to get the script wrong ;-) > > > > Sorry for all the commit noise; I think I've fixed all the incorrect fixes > now. > > > > <snip/> > > Thanks for the fixing [all] sebb.
I've now done the other Commons proper projects in trunk. There will be some other incorrect DOAP files in branches, but none of them are currently listed in files.xml so they won't affect the projects web-site. Also added Exec and Proxy to files.xml as they were missing. Of couse they might not all be up-to-date - that can be dealt with later. BTW, in case anyone has not used it yet, I just discovered the SVN --depth option. This comes in very handy for jobs such as this where one only wants to check out part of a directory tree - the depth is "sticky", i.e. is remembered. For example (pseudo-code): svn co commons/proper --depth immediates commons-proper cd commons-proper for each directory do svn co --depth files <directory>/trunk done > > -Rahul > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
