Just bitten by ITS#5794. As you could imagine I need to patch my server ASAP. That's what I did:
1. In the ITS page I see a message from hyc ack'ing the bug fix. 2. Have to dig openldap-commit message by message trying to hit days near hyc'message date 3. Got http://www.openldap.org/lists/openldap-commit/200811/msg00035.html saying passwd.c went from 1.141 to 1.142 and http://www.openldap.org/lists/openldap-commit/200811/msg00036.html saying passwd.c went from 1.142 to 1.143 4. Go to CVS web ui and request unidiff for passwd.c from 1.141 to 1.143. http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/passwd.c.diff?hideatt...
Questions: - Is there a way to have information that links 1 and 2 so I don't have to dig openldap-commit archive? - In case a fix spans several files how should I proceed?
Regards, maykel
--------------------------------------- Red Telematica de Salud - Cuba CNICM - Infomed
Maykel Moya wrote:
Just bitten by ITS#5794. As you could imagine I need to patch my server ASAP. That's what I did:
- In the ITS page I see a message from hyc ack'ing the bug fix.
- Have to dig openldap-commit message by message trying to hit days
near hyc'message date 3. Got http://www.openldap.org/lists/openldap-commit/200811/msg00035.html saying passwd.c went from 1.141 to 1.142 and http://www.openldap.org/lists/openldap-commit/200811/msg00036.html saying passwd.c went from 1.142 to 1.143 4. Go to CVS web ui and request unidiff for passwd.c from 1.141 to 1.143. http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/passwd.c.diff?hideatt...
Questions:
- Is there a way to have information that links 1 and 2 so I
don't have to dig openldap-commit archive?
At one time I suggested that commit messages with ITS#s in their logs should be automatically forwarded to the ITS, but others felt this would generate too much noise in the ITS. Personally I believe it would be better to have bug reports and their corresponding fixes tightly linked, but no one else seems to feel strongly about it. So for now, searching the commit archive is the only choice.
- In case a fix spans several files how should I proceed?
All patches related to a single issue will have the ITS# in their commit message. Most patches that affect multiple files in a single directory will have a single commit message, though occasionally it will be spread across multiple commits. Patches that span multiple directories, committed all at once, will have identical commit messages in each directory.
--On Thursday, November 20, 2008 2:31 PM -0800 Howard Chu hyc@symas.com wrote:
Maykel Moya wrote:
Just bitten by ITS#5794. As you could imagine I need to patch my server ASAP. That's what I did:
- In the ITS page I see a message from hyc ack'ing the bug fix.
- Have to dig openldap-commit message by message trying to hit days
near hyc'message date 3. Got http://www.openldap.org/lists/openldap-commit/200811/msg00035.html saying passwd.c went from 1.141 to 1.142 and http://www.openldap.org/lists/openldap-commit/200811/msg00036.html saying passwd.c went from 1.142 to 1.143 4. Go to CVS web ui and request unidiff for passwd.c from 1.141 to 1.143. http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/passwd.c.diff?hid eattic=1&r1=text&tr1=1.41&r2=text&tr2=1.143&f=u
Questions:
- Is there a way to have information that links 1 and 2 so I
don't have to dig openldap-commit archive?
At one time I suggested that commit messages with ITS#s in their logs should be automatically forwarded to the ITS, but others felt this would generate too much noise in the ITS. Personally I believe it would be better to have bug reports and their corresponding fixes tightly linked, but no one else seems to feel strongly about it. So for now, searching the commit archive is the only choice.
This is what we do at Zimbra, and it is extremely helpful. I keep hoping this will be added when we get rid of the current ITS system and upgrade to something else. Since we don't allow people to be CC'd in the current system anyway, most people wouldn't get much noise from it unless they were subscribed to the bugs list, and you get a lot of messages then anyway.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
El jue, 20-11-2008 a las 14:47 -0800, Quanah Gibson-Mount escribió:
This is what we do at Zimbra, and it is extremely helpful. I keep hoping this will be added when we get rid of the current ITS system and upgrade to something else. Since we don't allow people to be CC'd in the current system anyway, most people wouldn't get much noise from it unless they were subscribed to the bugs list, and you get a lot of messages then anyway.
Is there any plan to upgrade the current ITS system (and/or current VCS system)?
Regards, maykel
--------------------------------------- Red Telematica de Salud - Cuba CNICM - Infomed
Maykel Moya wrote:
El jue, 20-11-2008 a las 14:47 -0800, Quanah Gibson-Mount escribió:
This is what we do at Zimbra, and it is extremely helpful. I keep hoping this will be added when we get rid of the current ITS system and upgrade to something else. Since we don't allow people to be CC'd in the current system anyway, most people wouldn't get much noise from it unless they were subscribed to the bugs list, and you get a lot of messages then anyway.
Is there any plan to upgrade the current ITS system (and/or current VCS system)?
That's an unrelated question; no upgrade to ITS is needed just to integrate commit messages - we simply need to subscribe the ITS email address to the commit mailing list.
Howard Chu writes:
That's an unrelated question; no upgrade to ITS is needed just to integrate commit messages - we simply need to subscribe the ITS email address to the commit mailing list.
And dispatch to the right ITS on "ITS#" in the message body as well as in the Subject. Or copy the ITS# into the Subject: before sending.
What to do with commits with several ITS#'s in the commit message? Reject them unless escaped/quoted some way?
Hallvard B Furuseth h.b.furuseth@usit.uio.no wrote:
What to do with commits with several ITS#'s in the commit message? Reject them unless escaped/quoted some way?
Why not copy them to multiple ITS?
Hallvard B Furuseth wrote:
Howard Chu writes:
That's an unrelated question; no upgrade to ITS is needed just to integrate commit messages - we simply need to subscribe the ITS email address to the commit mailing list.
And dispatch to the right ITS on "ITS#" in the message body as well as in the Subject. Or copy the ITS# into the Subject: before sending.
I used a simpler kludge in our install: Add a "Subject: ITS#" line in the commit template. Fill in the number if you have one.
What to do with commits with several ITS#'s in the commit message? Reject them unless escaped/quoted some way?
Hardlink them into each referenced report.
openldap-software@openldap.org
-
Hallvard B Furuseth -
Howard Chu -
manu＠netbsd.org -
Maykel Moya -
Quanah Gibson-Mount