[GRASS5] cvs updates completed successfully.

Glynn Clements glynn.clements at virgin.net
Sat Sep 18 21:37:10 EDT 2004


Michael Barton wrote:

> > I'm referring to scripts/Makefile, not scripts/r.univar.sh/Makefile.
> 
> I was too. That's what's strange. I did look yesterday morning. In fact
> Hamish updated this Makefile a few days ago to have r.univar.sh. So I am
> baffled as to why it is now showing r.univar (with Hamish still listed as
> updating it). 

The log entry for that commit says:

	revision 1.26
	date: 2004/09/16 03:16:44;  author: hamish;  state: Exp;  lines: +1 -0
	re-enable (renamed) r.univar.sh

However, the actual change was:

	$ cvs diff -r 1.25 -r 1.26 scripts/Makefile
	Index: scripts/Makefile
	===================================================================
	RCS file: /grassrepository/grass51/scripts/Makefile,v
	retrieving revision 1.25
	retrieving revision 1.26
	diff -u -r1.25 -r1.26
	--- scripts/Makefile	22 Jul 2004 05:46:51 -0000	1.25
	+++ scripts/Makefile	16 Sep 2004 03:16:44 -0000	1.26
	@@ -31,6 +31,7 @@
	 	r.reclass.area \
	 	r.regression.line \
	 	r.shaded.relief \
	+	r.univar \
	 	v.build.all
	 
	 default: subdirs

> >> The reason for renaming it is that there is a binary module also named
> >> r.univar. According to Markus, r.univar (binary) will eventually have all
> >> the functionality (and more?) of r.univar.sh (script). However, it is still
> >> under development so we are keeping the script for awhile.
> > 
> > I was asking why you renamed the directory; I know why you renamed the
> > script.
> 
> I renamed the directory because I thought it ought to match the script.
> 
> If it is better to do it another way, please do so.

It would have been better to have kept the original directory, as that
would have preserved the history.

-- 
Glynn Clements <glynn.clements at virgin.net>




More information about the grass-dev mailing list