"Behind" indicates how many commits are in the dev that are not in the
current branch, and "ahead" indicates how many commits are in the current
branch that are not in dev.
I think the best way of figuring out whether a branch is worth
investigating more, is to try and merge dev into it. If there are no
conflicts, or they are simple to fix, then the branch can still be safely
merged into dev if that's the desired goal. If not, it's best to lose it as
it will hardly ever be useful.
I'm in favor of eliminating obsolete branches; they just create confusion.
In an ideal world branches should be created to work safely on something;
when it's done merge back into master (or dev in our case) and remove the
branch.
Raff
On Fri, Dec 16, 2016 at 9:19 AM, Syd Bauman
I don't get the behind/ahead bit entirely, either. I had not deleted some of my earlier branches as I thought someone had said we should hang on to them for historical purposes. In Subversion you could just leave them tucked into the /branches/ directory, and they didn't get in anyone's way. Is there any way to sequester them like that in git?
If not, I agree we should go through and trim those we can. But we (or at least I, for one) would like a recipe for how to go about asking "what is in this branch that is not in dev/?". -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived