I would like to set up a list for all cvs commits. Therefore, every time someone makes a commit to the repository, the commit comments get emailed to the list. Its handy to keep track of who is working on what.
I have the functionality already setup, I just need a list to point it to. IEM seems the logical location since every other list is there, but I can easily set it up on SourceForge too.
.hc
Hi Hans-Christoph, i have a script running at my local cvs servers which mirrors the repository to the SF cvs. Since i daily change things which then get commited the list would be flooded with comments. I'm sure that the other developers are equally productive so the mail list probably has too high a volume. Maybe it's better to have a web page somewhere which lists these commits? There, things could also be organized or sorted in some way.
good gain, Thomas
----- Original Message ----- From: "Hans-Christoph Steiner" hans@eds.org To: pd-dev@iem.kug.ac.at Sent: Thursday, October 02, 2003 5:51 AM Subject: [PD-dev] cvs-commit list
I would like to set up a list for all cvs commits. Therefore, every time someone makes a commit to the repository, the commit comments get emailed to the list. Its handy to keep track of who is working on what.
I have the functionality already setup, I just need a list to point it to. IEM seems the logical location since every other list is there, but I can easily set it up on SourceForge too.
.hc
http://at.or.at/hans/
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
Thomas Grill wrote:
Hi Hans-Christoph, i have a script running at my local cvs servers which mirrors the repository to the SF cvs. Since i daily change things which then get commited the list would be flooded with comments. I'm sure that the other developers are equally productive so the mail list probably has too high a volume.
well, i guess that digest-mode could handle this quite well.
Maybe it's better to have a web page somewhere which lists these commits? There, things could also be organized or sorted in some way.
fine.
mfg.as.dr IOhannes
Only actual commits would trigger an email, not just running 'cvs commit'. So for example, I just ran cvs2cl on externals/grill to get a ChangeLog, and this is the volume of messages that would be on the list:
2003-10-01 22:38 xovo
* py/: config-pd-msvc.txt, makefile.pd-msvc, py.vcproj: ""
2003-10-01 22:32 xovo
* flext/changes.txt: ""
2003-09-24 22:41 xovo
* fftease/config-pd-linux.txt, fftease/makefile.pd-linux, dyn/build-pd-linux.sh, dyn/config-pd-linux.txt, dyn/makefile.pd-linux: ""
2003-09-24 22:37 xovo
* xsample/config-pd-darwin.txt, xsample/makefile.pd-darwin, xsample/xsample.cw, xsample/maxmsp/xrecord~.help, py/config-pd-linux.txt, py/makefile.pd-linux: ""
2003-09-24 22:32 xovo
* flext/: config-pd-darwin.txt, flext.cw, makefile.pd-darwin, makefile.pd-linux: ""
2003-09-23 22:53 xovo
* pool/makefile.pd-linux: ""
2003-09-23 22:48 xovo
* flext/config-pd-linux.txt: ""
2003-09-23 22:39 xovo
* vasp/config-pd-linux.txt, vasp/makefile.pd-linux, xsample/config-pd-linux.txt, xsample/makefile.pd-linux, pool/config-pd-linux.txt, pool/makefile.pd-linux: ""
2003-09-23 22:34 xovo
* flext/: changes.txt, config-pd-linux.txt, makefile.pd-linux, source/flclass.h, source/fllib.cpp, source/flsupport.cpp, source/flsupport.h: ""
2003-09-18 22:41 xovo
* dyn/dyn.vcproj, vst/readme.txt: ""
That is not high at all. About 15 messages in 2 weeks. If you had digest mode on, it would be only 3 or 4 messages in 2 weeks. Since its an separate email list, subscribing is optional, and it would be easy to filter it to get only the info you want.
It won't add to the load on IEM's server much since it doesn't need to be archived, all of the info is in CVS.
.hc
On Thursday, Oct 2, 2003, at 05:23 America/New_York, Thomas Grill wrote:
Hi Hans-Christoph, i have a script running at my local cvs servers which mirrors the repository to the SF cvs. Since i daily change things which then get commited the list would be flooded with comments. I'm sure that the other developers are equally productive so the mail list probably has too high a volume. Maybe it's better to have a web page somewhere which lists these commits? There, things could also be organized or sorted in some way.
good gain, Thomas
----- Original Message ----- From: "Hans-Christoph Steiner" hans@eds.org To: pd-dev@iem.kug.ac.at Sent: Thursday, October 02, 2003 5:51 AM Subject: [PD-dev] cvs-commit list
I would like to set up a list for all cvs commits. Therefore, every time someone makes a commit to the repository, the commit comments get emailed to the list. Its handy to keep track of who is working on what.
I have the functionality already setup, I just need a list to point it to. IEM seems the logical location since every other list is there, but I can easily set it up on SourceForge too.
.hc
http://at.or.at/hans/
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
________________________________________________________________________ ____
"[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore
Hans-Christoph Steiner wrote:
I have the functionality already setup, I just need a list to point it to. IEM seems the logical location since every other list is there, but I can easily set it up on SourceForge too.
hi. i would set up another pd-list, called pd-cvs@iem.at if it is desired. this would keep all the lists handy at one place.
anyhow, now that my alternative services is finally finished i guess i will have more time for pd than in the last year.
probably we could migrate the CVS from sourceforge to iem (medium-term or long-term), which might be faster on the long run (but of course we cannot offer a compile farm)
mfg.asf.aser IOhannes
At 07:37 PM 2/10/2003, IOhannes m zmoelnig wrote:
probably we could migrate the CVS from sourceforge to iem (medium-term or long-term), which might be faster on the long run (but of course we cannot offer a compile farm)
I see this as a good thing, as IIRC, SourceForge's CVS for anonymous access is 24 hours behind what it should be.
---------------- Luke Yelavich AudioSlack Founder and main package maintainer Audio software packaged for the Slackware Linux Distribution http://www.audioslack.com luke@audioslack.com
On Thursday, Oct 2, 2003, at 06:20 America/New_York, Luke Yelavich wrote:
At 07:37 PM 2/10/2003, IOhannes m zmoelnig wrote:
probably we could migrate the CVS from sourceforge to iem (medium-term or long-term), which might be faster on the long run (but of course we cannot offer a compile farm)
I see this as a good thing, as IIRC, SourceForge's CVS for anonymous access is 24 hours behind what it should be.
They are in the middle of a big upgrade, so I think that their CVS service will get much better. They are adding 6 new servers, starting from the original 2. They already have two new ones in place and I think that the CVS service has gotten noticably better. So I think we stick it out with SF for a bit longer.
But there is something nice about having everything in one place.
.hc
On Thu, 2 Oct 2003, Hans-Christoph Steiner wrote:
At 07:37 PM 2/10/2003, IOhannes m zmoelnig wrote:
probably we could migrate the CVS from sourceforge to iem (medium-term or long-term), which might be faster on the long run (but of course we cannot offer a compile farm)
I see this as a good thing, as IIRC, SourceForge's CVS for anonymous access is 24 hours behind what it should be.
They are in the middle of a big upgrade, so I think that their CVS service will get much better. They are adding 6 new servers, starting from the original 2. They already have two new ones in place and I think that the CVS service has gotten noticably better. So I think we stick it out with SF for a bit longer.
But there is something nice about having everything in one place.
The strongest argument to have it on a private server is that it would be easier to rearrange it there, IMO. (removing old directories and adjusting the structure).
Guenter