Package: git-buildpackage Version: 0.9.37 Severity: wishlist Dear Maintainer,
The option --all is available for some commands (clone, pull) but not for push. To me it seems that 'gbp push' is not equivalent to 'git push --all', mainly when a clone does not show the pristine-tar branch at first and some updates are done on this branch. I faced something like: $ gbp clone g...@salsa.debian.org:Peutch-guest/tworld.git $ git branch * master upstream $ git pristine-tar commit ../tworld_2.3.0.orig.tar.gz $ gbp push and the pristine-tar commit was not pushed until a 'git push --all'. Regards, Patrice -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.13-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git-buildpackage depends on: ii devscripts 2.25.2 ii git 1:2.47.2-0.1 ii man-db 2.13.0-1 ii python3 3.13.1-2 ii python3-dateutil 2.9.0-3 ii python3-yaml 6.0.2-1+b1 ii sensible-utils 0.0.24 Versions of packages git-buildpackage recommends: ii pristine-tar 1.50+nmu2 ii python3-requests 2.32.3+dfsg-4 ii sbuild 0.88.3 Versions of packages git-buildpackage suggests: pn python3-notify2 <none> ii sudo 1.9.16p2-1 ii unzip 6.0-28 -- no debconf information
