I would contact Dmytro before deleting the branches. Easiest thing in git to ensure things are merged is "git branch --no-merged". As far as i know he worked on parallel downloads in the 1.8 branch which is probably quite a dramatic (yet very useful) change.
just my 2cts ;) cheers On Tue, Aug 23, 2011 at 5:04 PM, Harald Wellmann <[email protected]>wrote: > Am 23.08.2011 14:52, schrieb Andreas Pieber: > > More interesting is the additional branch here >> https://github.com/ops4j/org.**ops4j.pax.runner/network<https://github.com/ops4j/org.ops4j.pax.runner/network>. >> Not sure how far >> this one affects the master. I think the patch could be valuable but >> would break backward compatibility. So maybe releasing 1.7.5 and then >> switching to 1.8 merging the new branch (since there are also snapshot >> deps used). >> > > > I'm not quite sure which branch and which patch you're referring to. > > There are two branches, runner-1.8.x and dev-pax-runner-osgi. > > runner-1.8.x has two fixes for PAXRUNNER-350 and PAXRUNNER-388 which were > merged into master and released with Pax Runner 1.7.2. > > So I'd say this branch is obsolete. > > The other branch has a few commits with rather meaningless comments and no > references to JIRA issues. Is that the one you mean? If so, can you explain > the goal of this branch? > > > Best regards, > Harald > > ______________________________**_________________ > general mailing list > [email protected] > http://lists.ops4j.org/**mailman/listinfo/general<http://lists.ops4j.org/mailman/listinfo/general> > -- Toni Menzel Source <http://tonimenzel.com>
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
