Sounds like a plan that is fine with me given that this is just a minor
change.
2017-07-01 18:22 GMT+02:00 Stefan Bodewig :
> On 2017-06-30, Dominik Psenner wrote:
>
> > While working on the Jenkinsfile so that jjenkins builds all kinds of
> > branches for us I noticed that pr-11 made it into mas
On 2017-06-30, Dominik Psenner wrote:
> While working on the Jenkinsfile so that jjenkins builds all kinds of
> branches for us I noticed that pr-11 made it into master without us carving
> out a release.
It's been my fault. I committed it to master out of habit and merged it
to develop later whe
Hi
While working on the Jenkinsfile so that jjenkins builds all kinds of
branches for us I noticed that pr-11 made it into master without us carving
out a release. The change is no big deal and I just pushed changes to
master too in order to have jenkins build that branch for us. Is this
change in
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4net/pull/11
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user MarcelGosselin opened a pull request:
https://github.com/apache/logging-log4net/pull/11
(doc) Fix name of class LogicalThreadContext
Fix name of class LogicalThreadContext in Scopes section, words were
reversed.
You can merge this pull request into a Git repository by r
