We just upgraded our repository schema to 1.6 and I have been busy
marking some changes as already merged (using --record-only) and then
actually merging some newer changes. Now I notice that the mergeinfo for
the root of trunk (and many other subdirs) lists trunk as a source. Is
this normal? Is this okay? Can I safely delete it?
Also, I seem to have one bogus record that has a bad path...'repos'
should not be included in the path. Should I just delete this line from
the property?
Now that I've struggled through this, I wonder if anyone knows of a
getting started guide for updating a repository that does not have
mergeinfo. If there is, I'd like to contribute. If not, where should I
start one?
JLM
[jlm_at_zaz4 trunk]$ svn info .
Path: .
URL: svn://svn/zcode/trunk
Repository Root: svn://svn
Repository UUID: acbe0041-fb30-0410-9631-9a56e7159d43
Revision: 9638
Node Kind: directory
Schedule: normal
Depth: empty
Last Changed Author: jlm
Last Changed Rev: 9638
Last Changed Date: 2009-09-30 10:21:01 -0400 (Wed, 30 Sep 2009)
[jlm_at_zaz4 trunk]$ svn pg svn:mergeinfo .
/repos/zcode/trunk:8*
/zcode/branches/rel_2_1:8309-9341*,9605*,9633*
/zcode/branches/rel_2_2:9342-9626*,9637*
/zcode/trunk:9-8308*
Jeremy Mordkoff
Director, QA, IT & Release
ZeeVee, Inc.
One Monarch Drive | Littleton, MA 01460
Office: 978.467.1395 x233 | Fax: 978.467.1404
Mobile: 978-257-2183
jlm_at_zeevee.com
www.zeevee.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2402128
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-30 18:11:20 CEST