[prev in list] [next in list] [prev in thread] [next in thread]
List: subversion-issues
Subject: [Issue 4463] New - log -g --xml doesn't specify direction of merges.
From: breser () tigris ! org
Date: 2014-01-16 21:56:28
Message-ID: iz4463 () subversion ! tigris ! org
[Download RAW message or body]
http://subversion.tigris.org/issues/show_bug.cgi?id=4463
Issue #|4463
Summary|log -g --xml doesn't specify direction of merges.
Component|subversion
Version|1.8.x
Platform|All
URL|http://mail-archives.apache.org/mod_mbox/subversion-us
|ers/201401.mbox/%3C1B05D8F50421E24799AE93B03CC284BE020
|2B68587%40CRPMBX01.corp.cbeyond.net%3E
OS/Version|All
Status|NEW
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P3
Subcomponent|cmdline client
Assigned to|breser
Reported by|breser
------- Additional comments from breser@tigris.org Thu Jan 16 13:56:28 -0800 2014 \
------- svn log -g when dealing with reverse merges specifies the fact with the \
merged via line like so:
Reverse merged via: r17
--xml does not have a merged via line because the fact that a change is a merge
and the revision it was merged from is available via XML nesting, however the
fact that the merge is a reverse merge is not.
Reported via this thread on users@:
http://mail-archives.apache.org/mod_mbox/subversion-users/201401.mbox/%3C1B05D8F50421E24799AE93B03CC284BE0202B68587%40CRPMBX01.corp.cbeyond.net%3E
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=3071697
To unsubscribe from this discussion, e-mail: \
[issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic