Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] handling commit mails

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Eric Sandall <eric AT sandall.us>
  • To: "Jeremy Blosser (emrys)" <jblosser-smgl AT firinn.org>
  • Cc: SM Discuss <sm-discuss AT lists.ibiblio.org>
  • Subject: Re: [SM-Discuss] handling commit mails
  • Date: Mon, 24 Oct 2005 16:38:55 -0700 (PDT)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 24 Oct 2005, Jeremy Blosser (emrys) wrote:
Currently people who want to see our development traffic can subscribe to
commits in P4. People do this because they're just curious or because they
want/need to know if something changes in code they are responsible for or
take an interest in. Fairly often commits get commented on, and sometimes
these comments turn into discussions of reasonable length.

I would like to see these discussions get back to a tracked ML, both so our
development process stays as open as possible and so that there is a record
of any conclusions reached. We try to avoid making decisions in that forum
without taking it to the regular ML first, but sometimes people conclude
things anyway, or the same questions come up repeatedly without a reference
to previous answers.

I know that at one point we looked at setting up a regular ML for people to
subscribe to that would get all commit messages, but I don't think that
ever got finished. There's a list out there for sm-commits, but it
appears to get no real traffic. Is there any reason I shouldn't go ahead
and get this list receiving all commits? That way it would also be on the
cc list for any discussions that happened around commits, and we'd have a
record.

Instead of just one list, would there be any call for separate
sm-sorcery-commit, sm-cauldron-commit, and sm-grimoire-commit lists? That
would let people subscribe to just specific projects if they wanted to.
Alternately those commits could get sent to the existing sm-foo-bugs lists
we use in bugzilla.

I've setup the list and have been playing (when I have time) with the
Perforce user 'commit_ml_daemon' and the p4review.py[0] script, but
haven't had much success in getting the format I want.

There has been a request to have headers setup to define
'project[-grimoire-section]' (e.g. 'grimoire-devel-e') so that people
can setup filters for projects, grimoires (if applicable), and sections
(also if applicable). I haven't gotten to this part yet.

- -sandalle

[0] ftp://ftp.perforce.com/perforce/tools/p4review.py

- --
Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDXXCSHXt9dKjv3WERAvReAJ49pkQ6EGya0PKpf/ZawxFFsymbaQCfaPo8
blDHewCl8T3DTc5U70L1uNU=
=ZQTg
-----END PGP SIGNATURE-----




Archive powered by MHonArc 2.6.24.

Top of Page