[Greg Stein]
> But I'll go one step further: you shouldn't care at all.
>
> I could release 1.2.2 tomorrow with all kinds of crap. Or maybe the
> day after 1.8.0 goes final. Not much you can do about it. Subversion
> needs to soak its own code, not the entire dependency stack.
You could, but 1.2
On Mon, Jun 3, 2013 at 10:22 AM, C. Michael Pilato wrote:
>...
> On the other hand, Serf 1.2.0 is the only available public Serf release with
> which Subversion 1.8.0 can operate[2], which really rather limits folks'
>...
> Unfortunately, there is as yet no public Serf release to date which contai
On Mon, Jun 3, 2013 at 7:22 AM, C. Michael Pilato wrote:
> I'll suggest that the answer is found in how we'd track the issue locally.
> "Subversion requires Serf 1.2.1" would be a reasonable issue description.
> It would naturally be a 1.8.0 blocking issue. It's resolution (on our end,
> at least
3 matches
Mail list logo
