-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, 9 Sep 2018 17:59:19 +0200 Guido =?iso-8859-1?Q?G=FCnther?= <
a...@sigxcpu.org> 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...
> 
Hi,

I started using gbp push/pull recently and I'm also surprised by the current
behavior. What is the rationale for *not* pushing the Debian branch as part of
the push?

For me, gbp push semantics are: “just push everything needed”, but it's
obviously not the intended behavior. What is the intended behavior then?

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlu7husACgkQ3rYcyPpX
RFux4gf+O2W4z5q4fHNb5GSsI9ifqv4yZ8YDopsBWPrPO11sFV22akRzpb6W13p5
ebl5bBWIcrfY6gX85vZZaY2YD7zmq/pXGZn1eaI7rEHWA0SYgIyPqbreQcOPjkFJ
DZhj1DKV4pQJr2yvrLnm89u7xKqR+LZEBWwR2svRTxvwyY5VHZ7DuAGJj9jZX+dq
SIka5d46+vcGgyhB+93Wwee2+MM8EgyNFal+dDE0OOhN4NQBu7nt0m8O2CKlD+7p
a/GWDOUj1UlxA0bLi/PoAeiXBbkpHXz9HdbYjfqCyWmy+VD65K6wzTMtE9NSVwiR
7iYbZtJj7rSwj/LTyRXKu59Am1MNwA==
=+cgN
-----END PGP SIGNATURE-----

Reply via email to