
| Msg # 14944 of 15094 on ZZLI4416, Saturday 8-15-25, 8:36 |
| From: SEAN WHITTON |
| To: SEAN WHITTON |
| Subj: Bug#1111230: git-debpush: git-debpush -- |
From: spwhitton@spwhitton.name Hello, On Fri 15 Aug 2025 at 10:47pm +01, Sean Whitton wrote: > Package: git-debpush > Version: 13.11 > Severity: wishlist > > Hello, > > Currently I have a script which finalises changelogs and then does > > dgit push-source "$@" > git push --follow-tags --no-verify > > I want to replace this with just 'git debpush'. > > I think losing the --no-verify is right; there is no need for > git-debpush to ignore Git hooks just because it has made a tag (by > contrast, in the 'dgit push-source' case, the upload is already > finalised so I definitely want to push it no matter the hooks). > > But the --follow-tags seems useful. For example, for devscripts, I am > about to debpush 2.25.18, but in accordance with that package's > conventions I should also make a v2.25.18 tag. I wouldn't like to have > to remember to push this separately. git-debpush won't push it itself, > though, because it's a native package. > > Should git-debpush perhaps have a --follow-tags option which is just > passes straight through to git-push? Arguments against: - this is a very obscure case. if for example it's a non-native package where there are separate vNN tags made by the uploader, it'll push them - we want ordinary uploads to be optionless. I think I'm leaning towards *not* wanting to add this option. -- Sean Whitton --- SoupGate-Win32 v1.05 * Origin: you cannot sedate... all the things you hate (1:229/2) |
328,116 visits
(c) 1994, bbs@darkrealms.ca