Having fun. I just do push --path after clone --path - why it repush a lot of patches recorded after this particular one?

Remote already knows about them so useless (???) work happens.

Let's go. In and out, 20 minutes adventure.

$ cd pijul-tests
$ git pull
$ ./partial-all2.sh
# wait
$ cd ../pijul-tests-data
$ cd yesno/a/scripts/lxdialog/
$ pijul ls
a
a/scripts
a/scripts/lxdialog
a/scripts/lxdialog/yesno.c
$ echo "2" >> yesno.c
$ pijul rec -am.
$ pijul push --path a

# $EDITOR opens
#
# The following changes are new in the remote
# (and are not yet known to your local copy):
#
#     K65DDQXEPJ77AQJA223FJ3UVWHSYZXITFX6M2ZNNFGL2AM2C64SAC
#     PGIEKAK2IRMXWXZHGPDHHH7KE7T6YABPYIAY762B77JTB254WX3QC
#     MAG3ADJVH66ODZMHCG3S73D4OZ3QS7TYJDD2CKJWLB3S27AUKB3QC
#     EIBI6C5TIXDWD7NIBCRPZ4WP2W6FT5SSDKE5BGYCXV5G4YZ4HG4QC
#     L53C4RZRRTIGX4QNE77QA6EWZIZLFZVEJVO2WKHRNNG3DEHE66JAC
#     ... plus 34 more changes

# exit one $EDITOR second opens, save&exit
# wait long time with push
$ cd ../../../../
# you are in pijul-tests-data
$ pijul clone --path a/scripts/lxdialog/yesno.c repo yesno2
Repository created at /c/pijul-tests-data/yesno2
Downloading changes  [==================================================] 3/3 [00:00:00]
Applying changes     [==================================================] 3/3 [00:00:00]
Downloading changes  [==================================================] 3/3 [00:00:00]
Completing changes... done!                                                                
$ tail -1 yesno2/a/scripts/lxdialog/yesno.c
2
# successfull clone after clone-push
$

Check for useless work and close.