Path: csiph.com!3.eu.feeder.erje.net!feeder.erje.net!news.albasani.net!tahina.priv.at!bofh.it!news.nic.it!robomod From: Gordon Ball Newsgroups: linux.debian.maint.python Subject: Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes Date: Tue, 12 May 2020 08:50:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue May 12 06:49:44 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MONOTONE_WORDS_2_15=1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 X-Greylist: delayed 608 seconds by postgrey-1.36 at bendel; Tue, 12 May 2020 06:49:31 UTC Old-Dkim-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=chronitis.net; s=mythic-beasts-k1; h=Subject:To:From:Date; bh=yZU8nvQ9vColAJCIldkT1vzvrfYyBOHbgnqU7O4bGMQ=; b=CM/0np1IvGgePSM812Fq8ptgux zWk0q5ZZkKJmf7Fco6nhh2C3TebKhqqiK4pBXF+qdOWkVs79G23z3zoSjkyPtYcpwvFGMyylFgGL8 cjhRvcBvTz/c9ePm6CmXwXyqZrqtERWIOMhLXjIO1icOxX1K4VbnWe9ZHCyqGMaX1giDKNXIe9OsE mEqxHQU/SVy5tO9HhOmBUUKmk/+Zm29Jd5dQpqsNgfzh168weOm5TUvFG723uHd/FdQ4ka9b/n1eS 0fKDJjFtGoB5twLl5LPOD5dmMeoioWwXjQ5dVnLKlQf75h5/ObFrH65XnzyDCd2TGDEapy2T9ecGo 8CxVHYzg==; MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailing-List: archive/latest/18273 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20200512063906.fnxl56yqzhb44rkf@emissary.chronitis.net Approved: robomod@news.nic.it Lines: 48 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Antoine =?utf-8?Q?Beaupr=C3=A9?= , debian-python X-Original-Date: Tue, 12 May 2020 06:39:06 +0000 X-Original-Message-ID: <20200512063906.fnxl56yqzhb44rkf@emissary.chronitis.net> X-Original-References: <874ksldgwa.fsf@angela.anarc.at> Xref: csiph.com linux.debian.maint.python:12578 On Mon, May 11, 2020 at 10:37:47PM -0400, Sandro Tosi wrote: > > Any trick to avoid those errors in general? > You can also do $ gbp push which will automatically push the main (master or debian/master), upstream and pristine-tar branches. However, by default it does not push UNRELEASED changes (ie, the main branch only gets pushed if there is a release tag). It certainly helps to keep the upstream and pristine-tar branches up to date, however. There is also equivalently $ gbp pull $ gbp clone to ensure all of these branches are updated from the remote without the need to switch to them in turn and push/pull them. Gordon > when i push i always do > > $ git push --all ; git push --tags > > i also have these in ~/.gitconfig > > [push] > default = current > followTags = true > > with should make the `git push --tags` unnecessary after `git push > --all` (as tags will "follow" the diffs you're pushing) but it's stuck > in my bash history so there it is > > > Anyways, it should be there now! > > indeed it's there -- thanks! > > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > Twitter: https://twitter.com/sandrotosi >