On Tue, 26 Aug 2008, Junio C Hamano wrote: > "Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > > > Petr Baudis <pasky@xxxxxxx> wrote: > >> git <tab><tab> still shows way too many commands, some of them > >> are clearly plumbing. This patch hides the plumbing commands > >> liberally (that is, in special cases, users still might want to > >> call one of the hidden commands, a *normal* workflow should never > >> involve these, though - and if it does, we have a UI problem anyway). > >> > >> Signed-off-by: Petr Baudis <pasky@xxxxxxx> > > > > Acked-by: Shawn O. Pearce <spearce@xxxxxxxxxxx> > > > > Though I use git ls-remote at least once every other day to see > > what branches are available on my egit/spearce.git fork. Its ok, > > I guess I can type a few extra characters... > > Revision-requested-by: me > > Unless/until we have an easy way to obtain the information "git-ls-files > -u" gives during conflict resolution, ls-files should stay on the list of > commonly used commands. Doesn't "git status" tell you that? Or do you want the extra info from the implicit --stage? -Daniel *This .sig left intentionally blank* -- 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
