Karl Fogel wrote:
> "Mark Phippard" <markphip_at_gmail.com> writes:
>> I also saw some discussion last week about improving the format of the
>> mergeinfo output before release. Is that still an open issue or did
>> it get committed? When Dan and I were originally making proposals
>> around this command we envisioned it having output that was similar to
>> svn log. At the time, that was the main hold-up for us in
>> implementing it as we could not decide if it should be a new
>> subcommand or an option to log. I liked the proposals for the command
>> line UI I saw last week, but would still like to see log style output.
>> In the graphical merge client we have built, I use the API to show
>> the revisions eligible to be merged and I do it in a log style format.
>> It is extremely useful, especially when deciding what revisions ought
>> to potentially be backported.
>
> I think that discussion is still going on, but all the contenders have
> been implemented (as far as I know), so it's just a question about
> choosing what we want the output to look like.
>
>> As an example, I have attached the output we produce in the client of
>> some of our eligible revisions. We get 25 at a time, and I clicked
>> the Get Next button a couple of times until I saw the date was prior
>> to our recent releases. I am not proposing we follow this exact
>> output, just that it can make it easy to see what you might want to
>> merge when you can see it in log format. Someone might see some more
>> stuff to propose for backport in this output too :)
>
> I think that's roughly what one of the proposed verbose-ish outputs
> looks like, yeah.
>
>> Anyway, getting this back on topic. Are there any other blockers
>> besides the one (maybe two) issues I noted above? Proposed backports
>> notwithstanding of course.
>
> Aside from that, I know of none. My in-progress changes to fix
> libsvn_client/diff.c (to make diff_tests 47 pass, but the problem is
> with Subversion, not with the test) are not 1.5 blockers, IMHO. I
> should have them done today, and will propose them for backport, but
> they don't need to hold anything up.
>
> RC1 this week? :-) Hyrum?
That works for me. I'm going to be afk for most of the weekend, but
that shouldn't block folks if we roll on Thursday or Friday.
-Hyrum
Received on 2008-03-25 17:33:08 CET