|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-10449) Excluded regions do... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)
- [JIRA] (JENKINS-10449) Excluded regio... [email protected] (JIRA)

I'm not sure that this is a feature every user wants to have.
I for my case would like to see the whole changelog even if not every commit would trigger a new build.
So I think this should be configurable.
BTW: if you're in a situation like these and need to exclude certain regions, it might be a signal that your subversion repository should be modularized.