Re: [Python-modules-team] Processing of paramiko_2.7.1-1_source.changes
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
>
Reply to: