You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by Apache subversion Wiki <co...@subversion.apache.org> on 2013/02/13 17:26:03 UTC

[Subversion Wiki] Update of "MergeinfoCommand" by JulianFoad

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.

The "MergeinfoCommand" page has been changed by JulianFoad:
http://wiki.apache.org/subversion/MergeinfoCommand?action=diff&rev1=13&rev2=14

Comment:
Add a 'last changed rev' idea suggested by stsp; remove 'TODO' markers as not adding value.

  ||summary ||Summary in the form of a diagram (graph). || ||Done ||
  ||summary ||Show common origin of branches. || ||Done ||
  ||summary ||Show latest full merge (revnum and  direction). Initially, this only shows the "from" revnum; showing the "to" revnum is a separate requirement. || ||Done ||
- ||summary ||Show latest full merge in the other direction as well. Should be straightforward to extend the find_symmetric_merge set of functions to report both "base on source" and "base on target", and use them to mark the beginning of the two merge arrows. Of course, omit the arrow if there was no merge. ||day ||TODO ||
+ ||summary ||Show latest full merge in the other direction as well. Should be straightforward to extend the find_symmetric_merge set of functions to report both "base on source" and "base on target", and use them to mark the beginning of the two merge arrows. Of course, omit the arrow if there was no merge. ||day || ||
- ||summary ||Show the revnum of the "to" end of each merge arrow, as well as the "from" end. This info is not so easy to obtain.  The find_reintegrate_merge set of functions will need to scan the branch history for mergeinfo changes and find the first revision in which all the source revs ||week ||TODO ||
+ ||summary ||Show the revnum of the "to" end of each merge arrow, as well as the "from" end. This info is not so easy to obtain.  The find_reintegrate_merge set of functions will need to scan the branch history for mergeinfo changes and find the first revision in which all the source revs ||week || ||
- ||summary ||Show cherry-picks: shows whether there are any cherry-picks, in each direction, since the last full merge in the respective direction; and if so, indicates their revision number range(s) compactly. ||week ||TODO ||
+ ||summary ||Show cherry-picks: shows whether there are any cherry-picks, in each direction, since the last full merge in the respective direction; and if so, indicates their revision number range(s) compactly. ||week || ||
- ||summary ||Given a WC target, notice local mods (uncommitted merginfo). ||day ||TODO ||
+ ||summary ||Given a WC target, notice local mods (uncommitted merginfo). ||day || ||
- ||summary ||Indicate whether subtree info is being shown: at least, indicate if there might be relevant subtree mergeinfo that is not shown. ||week ||TODO ||
+ ||summary ||Indicate whether subtree info is being shown: at least, indicate if there might be relevant subtree mergeinfo that is not shown. ||week || ||
- ||summary ||Show subtree info when depth > empty. ||month ||TODO ||
+ ||summary ||Show subtree info when depth > empty. ||month || ||
- ||summary ||Abbreviate the branch path to just the branch name, somehow, and/or rearrange layout moving it to a separate line, so that a moderately long branch name does not overflow 80 columns. ||day ||TODO ||
+ ||summary ||Abbreviate the branch path to just the branch name, somehow, and/or rearrange layout moving it to a separate line, so that a moderately long branch name does not overflow 80 columns. ||day || ||
- ||summary||Indicate how many changes there are on each branch since the last merge. This would help a user to confirm what they're expecting, and/or evaluate whether a branch is in need of a catch-up merge.||days?||Wish||
+ ||summary ||Indicate how many changes there are on each branch since the last merge. This would help a user to confirm what they're expecting, and/or evaluate whether a branch is in need of a catch-up merge. ||days? || ||
+ ||summary ||Show the last changed revision on each branch (in addition to the head or specified tip revision, probably). ||day || ||
- ||--show-revs ||Show-revs mode with depth=infinity understandable & documented (in help). ||week? ||TODO ||
+ ||--show-revs ||Show-revs mode with depth=infinity understandable & documented (in help). ||week? || ||
  || || || || ||