As you can see a slightly adapted version of syncmail
(http://sourceforge.net/projects/cvs-syncmail/)
is running on the GRASS cvs server now.
It only generates emails for the modules web and grass right now.
Do you want commit messages for all modules?
On the topic above: I still believe that we should put ID
tags in files. The statement that this makes problems with
branches does not seem to be completly correct.
Bernhard
On Mon, May 13, 2002 at 08:42:36PM +0200, grass@intevation.de wrote:
Author: bernhard
Update of /grassrepository/grass
In directory doto:/tmp/cvs-serv8822
Modified Files:
SUBMITTING
Log Message:
SUBMITTING: added a "(?)" because the rule seems strange and I
want to test the new syncmail.
Index: SUBMITTING
RCS file: /grassrepository/grass/SUBMITTING,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- SUBMITTING 6 Mar 2002 16:24:49 -0000 1.21
+++ SUBMITTING 13 May 2002 18:42:34 -0000 1.22
@@ -55,7 +55,7 @@
The copyright protects your rights according to GNU General Public
License (www.gnu.org).
-4. - deleted. We don't want the $ ID $ in source code any more as it
+4. - deleted.(?) We don't want the $ ID $ in source code any more as it
causes problems for the CVS branches.
5. To ensure that the software system continues to work, please include
Bernhard Reiter wrote:
As you can see a slightly adapted version of syncmail
(http://sourceforge.net/projects/cvs-syncmail/)
is running on the GRASS cvs server now.
It only generates emails for the modules web and grass right now.
Do you want commit messages for all modules?
On the topic above: I still believe that we should put ID
tags in files. The statement that this makes problems with
branches does not seem to be completly correct.
It's not that big a deal. If I were doing another big merge, I'd just
check out everything with -kk. Keyword substitution is only really
important for generating source tarballs.
The worst case is $Log$, as the effects aren't restricted to the line
containing the keyword. In all other cases, you can use "diff -I ..."
to ignore differences caused by keyword substitution.
--
Glynn Clements <glynn.clements@virgin.net>
On Mon, May 13, 2002 at 09:04:07PM +0200, Bernhard Reiter wrote:
As you can see a slightly adapted version of syncmail
(http://sourceforge.net/projects/cvs-syncmail/)
is running on the GRASS cvs server now.
Congrats, Bernhard! Now the author is back in the mail, fine.
It only generates emails for the modules web and grass right now.
Do you want commit messages for all modules?
I don't think so - if you are open to add it later in case we
need it.
On the topic above: I still believe that we should put ID
tags in files. The statement that this makes problems with
branches does not seem to be completly correct.
Glynn was complaining here - he may decide.
Bernhard
On Mon, May 13, 2002 at 08:42:36PM +0200, grass@intevation.de wrote:
>
> Author: bernhard
>
> Update of /grassrepository/grass
> In directory doto:/tmp/cvs-serv8822
>
> Modified Files:
> SUBMITTING
> Log Message:
> SUBMITTING: added a "(?)" because the rule seems strange and I
> want to test the new syncmail.
>
>
> Index: SUBMITTING
> ===================================================================
> RCS file: /grassrepository/grass/SUBMITTING,v
> retrieving revision 1.21
> retrieving revision 1.22
> diff -u -d -r1.21 -r1.22
> --- SUBMITTING 6 Mar 2002 16:24:49 -0000 1.21
> +++ SUBMITTING 13 May 2002 18:42:34 -0000 1.22
> @@ -55,7 +55,7 @@
> The copyright protects your rights according to GNU General Public
> License (www.gnu.org).
>
> -4. - deleted. We don't want the $ ID $ in source code any more as it
> +4. - deleted.(?) We don't want the $ ID $ in source code any more as it
> causes problems for the CVS branches.
>
> 5. To ensure that the software system continues to work, please include
On Tue, May 14, 2002 at 08:33:20AM +0200, Markus Neteler wrote:
On Mon, May 13, 2002 at 09:04:07PM +0200, Bernhard Reiter wrote:
> It only generates emails for the modules web and grass right now.
> Do you want commit messages for all modules?
I don't think so - if you are open to add it later in case we
need it.
We are missing commit messages from the following modules:
libgrass
progmangrass50
commit messages are generated for:
grass
grass51
web
What is the reason not to have commit message for the former?
I can configure this easily, so we just need to find out.
On Tue, May 14, 2002 at 11:56:05AM +0200, Bernhard Reiter wrote:
On Tue, May 14, 2002 at 08:33:20AM +0200, Markus Neteler wrote:
> On Mon, May 13, 2002 at 09:04:07PM +0200, Bernhard Reiter wrote:
> > It only generates emails for the modules web and grass right now.
> > Do you want commit messages for all modules?
>
> I don't think so - if you are open to add it later in case we
> need it.
We are missing commit messages from the following modules:
libgrass
progmangrass50
commit messages are generated for:
grass
grass51
web
What is the reason not to have commit message for the former?
no reason...
I can configure this easily, so we just need to find out.
If easy, please go ahead.
Thanks,
Markus
On Tue, May 14, 2002 at 12:01:26PM +0200, Markus Neteler wrote:
On Tue, May 14, 2002 at 11:56:05AM +0200, Bernhard Reiter wrote:
> I can configure this easily, so we just need to find out.
If easy, please go ahead.
Done.