|
[
Permlink
| « Hide
]
lennon added a comment - 02/Jun/09 10:23 PM
I'm happy to look at this in more depth, but I'll need to know which project and repository are being affected, so I can look at the actual commit messages and try to determine the root cause.
Igor,
My apologies for the lag time on this. Unfortunately, I haven't yet been able to reproduce the particular in either my local development environment or our staging server, which has made fixing it somewhat of a challenge. I definitely hope to come up with a fix this sprint, but that would still push a deployed fix out until at least Monday the 22nd. If the lack of correct version information is impeding your workflow, I would suggest you do one of two things: either go ahead and disable the email entirely for the time being, or, a bit more drastically, delete the repository (but not your local clone), re-create it with the same name + permissions, and push the history back. If the problem truly is localized to your repository, that "hard reset" might resolve the issue, albeit at the cost of some time spent pushing changes back to the server. Again, I'm sorry for the delay, and will keep you posted on our progress as soon as I have more to report. Hi Lennon,
no worries, I can imagine that most of the kenai team was paralyzed during the j1 week, I was mainly looking for some estimate or workaround. I tried renaming the existing repo and creating a new one but I got stuck on http://kenai.com/jira/browse/KENAI-783 My repo is now "gone" and I can't recreate a new one with the same name (so that the whole team doesn't need to change repo uri). Is there something you can do to help plz? thanks a lot! /i So I recreated the repo and push all ~250 changesets into the empty repo on kenai, unfortunately it didn't change anything - for the "massive" push with 250 changesets I got one email for revision #5, and when I made one more changeset and pushed it, I got email for revision #6.
My best guess so far is that the mercurial changegroup script is not up-to-date. The behavior described indicates that we're passing a single revision into the commit notify procedure when we should be passing a list. I can make a code change for compatibility, but we should make sure the latest changegroup script is deployed every time.
Hopefully fixed in 0216524, but also note the issue about changegroup scripts.
Not yet in production, new deploy will be tonight.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Critical
Major inconsistencies in hg commit messages
