Jump to content

SiberianRobot

Members
  • Posts

    2
  • Joined

  • Last visited

SiberianRobot's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. We have a fairly large solution with many debug folders that should be excluded from source control. A simple */debug removes all of them just fine. Unfortunately, we also use boost which has a debug folder that we need. i.e. # include <boost/preprocessor/debug/error.hpp>. Is there a way to remove all directors with a given name with some absolute path exception? Thanks
  2. I am familiar with the show "Only relevant" option but I am hoping there is a way to designate particular CSs as relevant (or "Key" in the image below). I recently changed my philosophy on check-ins. This resulted in having more changes set as I want to minimize working on more than one bug/feature/improvement in one change set. However, the number of change sets could be less desirable for a code reviewer as many change sets may all be working towards a train of though (I am thinking: one Jira "story" can be thought of as many "tasks"). The biggest problem I see is that there is likely underdeveloped implementations as I am addressing a "task". I still want to get the isolation for the case when another person wants to look at smaller changes made for a subtask if they want a bit more clarification on what would otherwise be a much harder change set to follow. I hope that make sense. I would hope that when I select the "Only relevant" or some other existing functionality would generate the BranchCondensedToKeyCSs image below from the Current branch. I would also be interested in how to permanently condense two changeset (say: when I forget to include a newly added file or forgetting to save a last minute change, etc) Currently 50 versions behind but that is out of my control as I am not the admin. Thanks
×
×
  • Create New...