I agree on pruning old branches (especially once they're merged). I'll have to look at 809 because I think I made that one. Not sure on the other one, but that one might predate our git repo.
On 23 September 2014 08:43, Remko Popma <remko.po...@gmail.com> wrote: > I deleted the topic branch for LOG4J2-431 because it has been merged into > master so we don't need the bookmark any more. > > I gather that it is a common workflow to delete topic branches like this > after the work is done and they're merged into master. Shall we adopt that > workflow also? > > LOG4J2-577 and LOG4J2-809 are also closed in Jira. Does that mean that the > topic branches for these issues can be deleted? > > Sent from my iPhone > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > > -- Matt Sicker <boa...@gmail.com>
