Re: [PATCH v8 4/4] worktree: add 'list' command

On Tue, Sep 22, 2015 at 3:42 PM, Junio C Hamano wrote: > Michael Rappazzo writes: > >> >> +--porcelain:: >> + With `list`, output in an easy-to-parse format for scripts. >> + This format will remain stable across Git versions and regardless of >>

Re: [PATCH v8 4/4] worktree: add 'list' command

Mike Rappazzo writes: > ... Does the porcelain > format restrict additive changes? That is, is it OK for a future > patch to add another field in the format, as long as it doesn't alter > the other values? Is the format that I have used here acceptable > (assuming the

Re: [PATCH v8 4/4] worktree: add 'list' command

Michael Rappazzo writes: > > +--porcelain:: > + With `list`, output in an easy-to-parse format for scripts. > + This format will remain stable across Git versions and regardless of > user > + configuration. ... and exactly what does it output? That would be

[PATCH v8 4/4] worktree: add 'list' command

'git worktree list' iterates through the worktree list, and outputs details of the worktree including the path to the worktree, the currently checked out revision and branch, and if the work tree is bare. There is also porcelain format option available. Signed-off-by: Michael Rappazzo