22 AM, Johnson, Eric wrote:
I was wondering the same thing about the migration guide
-Original Message-
From: Eoghan Glynn [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2008 10:10 AM
To: dev@cxf.apache.org
Subject: Re: Tracking trunk commits blocked wrt to the 2.0.x_fixes
branch
I was wondering the same thing about the migration guide
-Original Message-
From: Eoghan Glynn [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 17, 2008 10:10 AM
To: dev@cxf.apache.org
Subject: Re: Tracking trunk commits blocked wrt to the 2.0.x_fixes
branch
Thanks Dan & Fre
Thanks Dan & Freeman,
Both suggested methods give exactly the same results.
A total of well over blocked 500 commits ... ouch, that's a lot to go
thru manually.
BTW what's general feeling on the completeness of the 2.1 Migration
Guide[1] wrt capturing potential compatibility issues?
Cheer
It's all stored as properties on the directory. Thus:
svn propget svnmerge-blocked .
would give you the list of revisions. THAT said, the stuff gnodet,
Freeman, and Willem have merged without using svnmerge.py may appear
in that list.
On a related note: I'm not using subversion 1.5
Hi Eoghan,
I guess what you want is "svnmerge.py avail -B", which will showthe
blocked revision list.
Regards
Freeman
Eoghan Glynn wrote:
Folks,
Does anyone know if svnmerge.py can be used to report on the commits
to trunk that have been "blocked" wrt to merging out to the
2.0.x_fixes b
