Jonathan Nieder <jrnieder@xxxxxxxxx> writes: >> +-S:: >> +--update-sparse-checkout:: >> + An editor is invoked to let you update your sparse checkout >> + patterns. The updated patterns will be saved in >> + $GIT_DIR/info/sparse-checkout. The working directory is also >> + updated. An empty file will abort the process. > > Wording nit: this doesn't make the worktree more up-to-date. How > about: > > --edit-sparse-checkout > --define-work-area > --narrow-worktree > > Hmph. > > --edit-sparse-checkout seems best for consistency of the choices I can > think of. "--change-sparse-checkout"? Onna-account of "edit" sounding like you're actually somehow editting the checkout itself... OTOH, since it invokes the editor... hmmm BTW, wouldn't it be more convenient to allow specifying patterns directly via the command line? I'd think in many (maybe the majority of) cases people will really only want one entry, and having to edit a file to specify it seems vaguely annoying... -Miles -- .Numeric stability is probably not all that important when you're guessing. -- 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