[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] commit list
|
> > Great idea, Tom. I'm having a hard time understanding
> where development
> > activity is taking place (short of looking at the revision
> history of
> > individual files). I remember agreeing that all commits
> would be published
> > to the patch list, but as you mention, that doesn't appear
> to be happening
> > and it's probably a little heavy weight at this time
> anyway. Having an
> > automated mechanism to do this would make life a lot easier.
>
> Amen to that!
> Doing this manually is a real burden, especially if your developement
> system is not hooked to the mail server and Cut/Paste to the
> system clipboard
> is not working.
>
> Asking for developers to manually send in patches for
> __every__ commit is
> ... well .. I do not have that kind of discipline.
Hey, you were starting to get into the groove :-)
>
>
> Did someone sent mail to webmaster@xxxxxxxxxxx or
> to our PMC(grand pooba sebastien)?
I saw the traffic, I'm trying to figure out how to automate it.
As Tom points out, this should all be doable with some scripts
hooked to the cvs commit command.
Tom, can you first email the scripts so we can figure out how
to hook it into the cvs server? I don't want to create the mailing list
until we're sure we can hook into the current eclipse infrastructure.
Thanks,
Seb
>
>
> >
> > Doug Schaefer
> >
> >
> > -----Original Message-----
> > From: Tom Tromey [mailto:tromey@xxxxxxxxxx]
> > Sent: Monday, October 07, 2002 6:32 PM
> > To: cdt-dev
> > Subject: [cdt-dev] commit list
> >
> > Let's set up a cvs commit mailing list.
> >
> > The idea is a mailing list to which notification of all cvs
> commits is
> > sent. There are several ways to set up such a list; one
> common way is
> > to list all the changed files along with the log message.
> >
> > Many projects have such a list. For instance, gcc has one (actually
> > it has several); you can see the archive here:
> >
> > http://gcc.gnu.org/ml/gcc-cvs/
> >
> > As you can see, messages to the gcc list also include cvsweb URLs
> > pointing to the actual changes.
> >
> > A list like this is a helpful adjunct to a patch list (even when the
> > patch list is being used, which right now it is not). A
> patch list is
> > nice to see what is about to happen, or might happen, plus
> discussion
> > of such things. A cvs list is nice for showing exactly what did
> > happen.
> >
> > A cvs commit list would be useful to me right now. I'm experiencing
> > some odd problems with the CDT, problems which didn't occur
> in a build
> > from last week. If I had an easier way to see what had changed, I'd
> > have more luck tracking down the problem change.
> >
> > If someone can set up the mailing list, I will be happy to
> supply the
> > cvs scripts and know-how to make it all work.
> >
> > Tom
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> > ------_=_NextPart_001_01C26EC6.BDF8BBD0
> > Content-Type: text/html
> > Content-Transfer-Encoding: quoted-printable
> >
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> > <HTML>
> > <HEAD>
> > <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> > charset=3DUS-ASCII">
> > <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
> > 5.5.2654.19">
> > <TITLE>RE: [cdt-dev] commit list</TITLE>
> > </HEAD>
> > <BODY>
> >
> > <P><FONT SIZE=3D2>Great idea, Tom. I'm having a hard time =
> > understanding where development activity is taking place (short of =
> > looking at the revision history of individual files).
> I remember =
> > agreeing that all commits would be published to the patch
> list, but as =
> > you mention, that doesn't appear to be happening and it's
> probably a =
> > little heavy weight at this time anyway. Having an automated =
> > mechanism to do this would make life a lot easier.</FONT></P>
> >
> > <P><FONT SIZE=3D2>Doug Schaefer</FONT>
> > </P>
> > <BR>
> >
> > <P><FONT SIZE=3D2>-----Original Message-----</FONT>
> > <BR><FONT SIZE=3D2>From: Tom Tromey [<A =
> >
> HREF=3D"mailto:tromey@xxxxxxxxxx";>mailto:tromey@xxxxxxxxxx</A>
> ] </FONT>
> > <BR><FONT SIZE=3D2>Sent: Monday, October 07, 2002 6:32 PM</FONT>
> > <BR><FONT SIZE=3D2>To: cdt-dev</FONT>
> > <BR><FONT SIZE=3D2>Subject: [cdt-dev] commit list</FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2>Let's set up a cvs commit mailing list.</FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2>The idea is a mailing list to which
> notification of =
> > all cvs commits is</FONT>
> > <BR><FONT SIZE=3D2>sent. There are several ways to
> set up such a =
> > list; one common way is</FONT>
> > <BR><FONT SIZE=3D2>to list all the changed files along with
> the log =
> > message.</FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2>Many projects have such a list. For
> instance, =
> > gcc has one (actually</FONT>
> > <BR><FONT SIZE=3D2>it has several); you can see the archive =
> > here:</FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2> <A =
> > HREF=3D"http://gcc.gnu.org/ml/gcc-cvs/"; =
> > TARGET=3D"_blank">http://gcc.gnu.org/ml/gcc-cvs/</A></FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2>As you can see, messages to the gcc list
> also include =
> > cvsweb URLs</FONT>
> > <BR><FONT SIZE=3D2>pointing to the actual changes.</FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2>A list like this is a helpful adjunct to
> a patch list =
> > (even when the</FONT>
> > <BR><FONT SIZE=3D2>patch list is being used, which right now it is =
> > not). A patch list is</FONT>
> > <BR><FONT SIZE=3D2>nice to see what is about to happen, or might =
> > happen, plus discussion</FONT>
> > <BR><FONT SIZE=3D2>of such things. A cvs list is nice
> for showing =
> > exactly what did</FONT>
> > <BR><FONT SIZE=3D2>happen.</FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2>A cvs commit list would be useful to me right =
> > now. I'm experiencing</FONT>
> > <BR><FONT SIZE=3D2>some odd problems with the CDT, problems which =
> > didn't occur in a build</FONT>
> > <BR><FONT SIZE=3D2>from last week. If I had an easier
> way to see =
> > what had changed, I'd</FONT>
> > <BR><FONT SIZE=3D2>have more luck tracking down the problem =
> > change.</FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2>If someone can set up the mailing list, I
> will be =
> > happy to supply the</FONT>
> > <BR><FONT SIZE=3D2>cvs scripts and know-how to make it all
> work.</FONT>
> > </P>
> >
> > <P><FONT SIZE=3D2>Tom</FONT>
> > <BR><FONT =
> > SIZE=3D2>_______________________________________________</FONT>
> > <BR><FONT SIZE=3D2>cdt-dev mailing list</FONT>
> > <BR><FONT SIZE=3D2>cdt-dev@xxxxxxxxxxx</FONT>
> > <BR><FONT SIZE=3D2><A =
> > HREF=3D"http://dev.eclipse.org/mailman/listinfo/cdt-dev"; =
> >
> TARGET=3D"_blank">http://dev.eclipse.org/mailman/listinfo/cdt-
> dev</A></F=
> > ONT>
> > </P>
> >
> > </BODY>
> > </HTML>
> > ------_=_NextPart_001_01C26EC6.BDF8BBD0--
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
>
>
> --
> au revoir, alain
> ----
> Aussi haut que l'on soit assis, on n'est toujours assis que
> sur son cul !!!
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
