t5318: test '--stdin-commits' with '--[no-]progress'
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | t5318: use 'test_must_be_empty't/ | +4 | 2 replies | |
| 2/2 | t5318: test that '--stdin-commits' respects '--[no-]progress't/ | +21 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] t5318: test '--stdin-commits' with '--[no-]progress'
Here's a short pair of patches that I wrote this morning after looking at Stolee's most recent coverage report.
The first patch is just cleanup, and the second patch is the real change. It would have been nice to parameterize these tests over the arguments to 'git commit graph' (ie., have three tests for 'write', 'verify', and 'write --stdin-commits'), but '--stdin-commits' is special since it requires input.
These patches are based off the tip of 'next', but really only need my changes from 'tb/commit-graph-no-check-oids'.
Taylor Blau (2):
t5318: use 'test_must_be_empty'
t5318: test that '--stdin-commits' respects '--[no-]progress'
t/t5318-commit-graph.sh | 29 +++++++++++++++++++++++++---- 1 file changed, 25 insertions(+), 4 deletions(-)
--
2.26.2.1052.gcc6b3749ab