poudriere-ports(8) verbosity when listing trees

[grahamperrin]

Please, should output with -v be more verbose?

% poudriere ports -l
PORTSTREE   METHOD    TIMESTAMP           PATH
default     git+https 2021-12-02 05:05:09 /usr/local/poudriere/ports/default
portoverlay -                             /usr/local/poudriere/ports/portoverlay
% poudriere ports -l -v
PORTSTREE   METHOD    TIMESTAMP           PATH
default     git+https 2021-12-02 05:05:09 /usr/local/poudriere/ports/default
portoverlay -                             /usr/local/poudriere/ports/portoverlay
% pkg info -x poudriere
poudriere-devel-3.3.99.20211017_2
% 

https://github.com/freebsd/poudriere/wiki/poudriere-ports.8-devel#OPTIONS

I can get the git hash by beginning then cancelling a bulk run, and I can get a status as shown below, is there (also) some way of getting the status of a tree with a poudriere command?

Thanks

% git status /usr/local/poudriere/ports/default
On branch main
Your branch is up to date with 'origin/main'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        x11/nvidia-driver/files/extra-patch-src_nvidia_nv-freebsd.h
        x11/nvidia-driver/files/extra-patch-src_nvidia_nvidia__ctl.c
        x11/nvidia-driver/files/extra-patch-src_nvidia_nvidia__dev.c
        x11/nvidia-driver/files/extra-patch-src_nvidia_nvidia__subr.c
        x11/nvidia-driver/files/patch-src_nvidia_nv-freebsd.h
        x11/nvidia-driver/files/patch-src_nvidia_nvidia__ctl.c
        x11/nvidia-driver/files/patch-src_nvidia_nvidia__dev.c
        x11/nvidia-driver/files/patch-src_nvidia_nvidia__subr.c


It took 13.25 seconds to enumerate untracked files. 'status -uno'
may speed it up, but you have to be careful not to forget to add
new files yourself (see 'git help status').
nothing added to commit but untracked files present (use "git add" to track)
% 

[grahamperrin]

Getting the status of a tree

… I can get the git hash by beginning then cancelling a bulk run, …

Simpler (an answer): the git-rev-parse(1) example at #968 (reply in thread).