Hi, On Sun, Sep 09, 2018 at 05:59:19PM +0200, Guido Günther wrote: > Hi, > On Sun, Sep 09, 2018 at 10:45:35PM +0900, Norbert Preining wrote: > > Hi Guido, > > > > > See the man page. > > > > Ok, was that always like this? I faintly remember (but without > > screenshot to prove it) that I could gbp push stuff even without a > > tagged debian release!? > > It pushes everything *except* for the tip of your packaging branch (that > is any tags needed, upstream and pristine tar. > > > > > not up to date. If this does not happen it's a bug but pushing non > > > uptodate debian packaging branch is not the focus. > > > > ? I don't get what you want to say? I want gbp push to push the branches > > that are normally used by gbp (master/upstream/pristine-tar) and push > > any tag from gbp tag that isn't up there. > > And it does that, see this test: > > > https://github.com/agx/git-buildpackage/blob/master/tests/component/deb/test_push.py#L106 > > > Is this so unreasonable? > > > > Maybe I am the only developer on this earth that uses two computers and > > prefers to push/pull, but I was more than once beaten by a not pushed > > pristine-tar branch... > > Don't think so.
Would 'gbp push' getting a '--tips' option to just pushes the tips of upstream, debian and pristine-tar branch help? Cheers, -- Guido > -- Guido
