refactoring a branch with e.g. meld how?

I've been asked to seriously reorganize and compress a big branch (75 commits) What I'd like to do is make branches foo_flattened with all commits and branch foo_reorganized starting at the ancestor, then work by incrementally doing meld/commit/meld/commit/etc from foo_flattened into foo_reorganiz

gitk should maybe keep focus on same file when switching patch->tree view

if you're looking at the patch for a given file (have it selected in the lower right window), then when you switch to tree it would be nice if it started at that file. I realize you can view Old version/New version but that doesn't help with landing the the right level of the tree for projects wit

make notes show up in gitk graph view?

I'd like to be able to mark dysfunctional stuff that ended up in the repo but we don't want to delete with DONT_USE or something, and have it show up like tags do, but not have to be unique. If git notes don't work for this purpose maybe something else does? -- To unsubscribe from this list: send

is there interest in tooltip patches for gitk?

or would they be regarded as too tricky to keep in sync with reality/other documentation? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: strange behavior with nonexistant or partially populated ~/.config/git/gitk

My bad, problem was I missed existence of .gitk (used only if ~/.config/git/gitk doesn't exist). On Fri, Feb 5, 2016 at 6:16 PM, Britton Kerin wrote: > If ~/.config/git/gitk doesn't exist, I get small fonts (fine) and ugly > hard-to-read dark green branch labels. > > The

strange behavior with nonexistant or partially populated ~/.config/git/gitk

If ~/.config/git/gitk doesn't exist, I get small fonts (fine) and ugly hard-to-read dark green branch labels. The fix for the dark green problem is here: http://stackoverflow.com/questions/26025810/gtk-apps-show-green-too-dark But after doing: echo 'set headbgcolor lime' >~/.config/g

Re: no luck with colors for branch names in gitk yet

On Fri, Feb 5, 2016 at 12:25 PM, Philip Oakley wrote: > From: "Britton Kerin" >> >> Someone suggested using color.branch.upstream, I tried like this and >> variants >> >> [color "branch"] >> local = red bold >> upstream =

no luck with colors for branch names in gitk yet

Someone suggested using color.branch.upstream, I tried like this and variants [color "branch"] local = red bold upstream = red bold Doesn't seem to matter what I put in for upstream, including invalid colors, gitk just ignores it and does the dark green for local branches -- To unsubscribe fr

changing colors in the tree view in gitk

I upgraded from 2.5 to 2.7 and the branch names went from a light green to dark green, the names of the tags are hard to read now. Is it possible to configure the branch name color in the tree view? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to major

gitk view documentation? tooltips?

I guess I found the view documentation in git-log and git-rev-list man pages For some reason my brain also slightly resists permanently learning what some of the arrows, search, find fields etc at the top level do. Might tooltips for all this stuff be helpful? -- To unsubscribe from this list: se