Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-3981

Allow tracing a hunk through future history

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Suppose I have searched for a particular change and located it in the search pane. I can "view in full log" but if it was a long time ago it is hard to trace it forward and figure out which branches have this change (or whether some later change has removed it). I would like more help tracking down why a fix is not present in a particular branch.
      Some ideas:

      • A command (or even a column in the search window) that tells me whether a particular change has been merged into the current branch (i.e., it's somewhere in the ancestors of the current branch tip).
      • A command that looks at a particular hunk and shows a list (or tree diagram?) of all the branches it has been merged into.
      • A command on a hunk that tells me the status of this hunk in the current branch. This would show me the chain of commits by which it was merged into my current branch, if it has been (or tell me it has not); it would also show any later commits that have modified this same region of code.

              Unassigned Unassigned
              bc4ef08d0245 John Thomson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: