[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN 1.5 and RC1

From: Paul Burba <ptburba_at_gmail.com>
Date: Mon, 24 Mar 2008 13:26:28 -0400

2008/3/24 Mark Phippard <markphip_at_gmail.com>:
> I was off-line most of last week while at EclipseCon and am just
> trying to get caught up on where things stand in terms of release. I
> saw that the svnserve 1.4 problem has been committed and proposed for
> backport. What other blockers do we have? I see we have at least
> one:
>
> Issue: 3133 - 'svn cp wc wc' requires repository access
>
> Is anyone specifically looking into this? I am kind of assuming that
> cmpilato might be, but am just checking.

Fixed that this morning, r30020, it has already been back ported to 1.5.x.

> 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.
>
> 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 :)
>
> 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.
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-24 18:26:43 CET

This is an archived mail posted to the Subversion Dev mailing list.