On Mon, Feb 16, 2009 at 22:12, Tilo Schwarz <tilo@xxxxxxxxxxxxxxx> wrote: > On Mon, 16 Feb 2009 00:47:05 +0100, Jonas Fonseca <jonas.fonseca@xxxxxxxxx> > wrote: > >> I have thought about it. The question is if a separate view is >> necessary or if the main view would do. > > I'm not sure if I understood it correctly. Do you mean, only commits are > shown, which are heads of some branch? If so, what if more than one head > points to the same commit? True, it is not very intuitive with more than one branch perhaps. However, I still think there is some overlap between a branch view, the main view and possible also the status view. From the status view you might want to create a new branch based on changes, and in the main view you might want to create a branch to help backport a bugfix. > I think I would prefer a branch view, because then one could also have a > branch-view keymap with specialized commands. One possibility would be (just > as example): Maybe it is best to keep it simple and focus on your idea first and make tig at least aware of branches. And yes, it makes sense with an new keymap. > The view shows something like this (here an example from the tig git > repository) > > master > * my_feature_bar > X my_feature_foo > origin/HEAD > origin/master > origin/release OK, I have added the begining structure for a branch view, bound to 'H' by default. It does not support any actions besides refreshing and viewing the branch history. So there is still some work to achieve the easy access to branch commands. >> bind main A !git branch %(prompt:^wip/[a-z-]+$:Name) %(commit) > > Ahh, ok, so tig would issue a prompt and ask me for the name? Yeah, I don't know if it will be useful. > BTW, is the git list the right list to discuss bugs / patches for tig? Yes please. -- Jonas Fonseca -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
