I vote that "m m" be "merge automatically", since that's the default action for "git merge". Similarly, I feel like it might make sense to make "f f" correspond to "git fetch", although I feel less strongly about that.
Other than that I like Moritz's suggestions. On Fri, Aug 6, 2010 at 12:24 AM, Moritz Bunkus <[email protected]> wrote: > Hey, > > Great, great stuff! Though I haven't tried it I'm very, very much in > favor of this system. I'll try to testdrive it this weekend. > > > Right now it supports the commands under the `log' and `branch' groups, > > so pressing `l' shows a menu for setting options and launching > > commands. For branches that's `b'. Short log becomes `l l', long log 'l > > L', short log for all branches is `l a l' etc. It is not mandatory to > > relate a menu group with a keybinding on magit's status buffer, though, > > you can do M-x magit-log and it has the same effect. > > For log I'd like to be able to set the initial number of log entries to > a rather low number and add more entries with something like 'l m' (log > more?). This has been discussed in the past and I'm not certain about > the current status, and it also doesn't really belong into this > discussion, but I just remembered it :) > > > So far some people expressed enthusiasm about the concept, but > > otherwise received zero feedback. It would be important to determine > > which groups deserve to be created (I have on mind one for > > fetching/pulling) > > Definitely. Maybe for fetching/pulling: > > 'f a' -- "fetch all" aka "git remote update" > > 'f r' -- "fetch one remote" aka "git fetch <name>" > > 'f p' -- "pull" aka "git pull" (or maybe 'f f' to make it easier to > type) > > Pushing: > > 'p p' -- "push" aka "git push <tracked remote>" > > 'p r' -- "push to named remote" aka "git push <named rev> <named > remote/named other rev>" > > 'p t' -- "push tag" with tag selection and remote selection aka "git > push tags/<named tag> <named remote>" with <named remote> defaulting to > <tracked remote>. Or maybe this could become 'p t r' with 'tag' being a > modifier like your 'all' example from above. > > Merging: > > 'm m' -- This could either be 'manual merge' or 'automatic merge' > depending on the user's wishes. I guess 'm' for 'm'anual would be easier > to remember. So 'm m' as manual merge and... > > 'm a' -- Automatic merge > > 'i i' -- Ignore item (add to .gitignore) > > 'i l' -- Ignore item locally (add to .git/info/exclude) > > 'i ? i' -- Ask which item to ignore (e.g. so that the user can add a > directory name) > > 'i d' -- Ignore directory this item is in (add to .gitignore) ? :) Or > maybe make this a modifier, too: 'i d i' and 'i d l'. > > Staging: I'm not sure whether or not I'd like to prefix 's'. I guess not > as you use it all the time. However, we could have: > > 'S c' -- stage all changed > > 'S u' -- stage all untracked > > 'S a' -- stage all changed & all untracked > > 'z z' -- stash > > 'z s' -- stash snapshot > > Regards, > Mosu > > -- > If Darl McBride was in charge, he'd probably make marriage > unconstitutional too, since clearly it de-emphasizes the commercial > nature of normal human interaction, and probably is a major impediment > to the commercial growth of prostitution. - Linus Torvalds >
