Groups > linux.debian.maint.python > #10837

Re: Salsa repository and first upload of tinyarray

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Piotr Ożarowski <piotr@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Salsa repository and first upload of tinyarray
Date	Wed, 22 Aug 2018 14:30:01 +0200
Message-ID	<wpAqR-7up-7@gated-at.bofh.it> (permalink)
References	<wpwGB-5hs-9@gated-at.bofh.it> <wpyp3-6lD-5@gated-at.bofh.it> <wpA7v-7op-1@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Wed Aug 22 12:22:34 2018
Old-Return-Path	<piotr@ozarowski.pl>
X-Amavis-Spam-Status	No, score=-6.979 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight	DYN_NJABL=ERR(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5 BL_NJABL=ERR(-1.5) CL_IP_EQ_FROM_MX=-3.1; rate: -6.1
Mail-Followup-To	debian-python@lists.debian.org
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Content-Disposition	inline
User-Agent	NeoMutt/20180223
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/16258
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/20180822122206.22fzwun35s5y37yf@sar0.p1otr.com
Approved	robomod@news.nic.it
Lines	21
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 22 Aug 2018 14:22:06 +0200
X-Original-Message-ID	<20180822122206.22fzwun35s5y37yf@sar0.p1otr.com>
X-Original-References	<87efeqvmll.fsf@grothesque.org> <CAOO6c=zNPMua7YPgBsE2fgapQKWxFxGprGi3x1KGY+4coXG0ng@mail.gmail.com> <8736v6vc85.fsf@grothesque.org>
Xref	csiph.com linux.debian.maint.python:10837

Show key headers only | View raw

> I've also kept the full upstream history in the upstream branch,
> assuming this to be more robust and powerful.  For example, this allows
> to directly cherry-pick commits into the patch queue.

you can add remote repository and cherry-pick upstream commits as you
like

> Since both these practices are discouraged by the policy, I'm ready to
> give them up,

please do

> but before I spend time working on it, I would like to ask
> whether tinyarray could be exempt from any one of both rules.  According
> with the policy, I would provide a debian/README.source file with the
> above rationale and instructions.

having one workflow makes it a lot easier to work on team packages,
please don't add exceptions if they're not really needed
-- 
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Thread

Salsa repository and first upload of tinyarray Christoph Groth <christoph@grothesque.org> - 2018-08-22 10:30 +0200
  Re: Salsa repository and first upload of tinyarray Ondrej Novy <novy@ondrej.org> - 2018-08-22 12:20 +0200
    Re: Salsa repository and first upload of tinyarray Christoph Groth <christoph@grothesque.org> - 2018-08-22 14:10 +0200
      Re: Salsa repository and first upload of tinyarray Piotr Ożarowski <piotr@debian.org> - 2018-08-22 14:30 +0200
      Re: Salsa repository and first upload of tinyarray Ondrej Novy <novy@ondrej.org> - 2018-08-22 14:40 +0200
        Re: Salsa repository and first upload of tinyarray Christoph Groth <christoph@grothesque.org> - 2020-08-26 16:40 +0200
  Re: Salsa repository and first upload of tinyarray Ondrej Novy <novy@ondrej.org> - 2018-08-22 12:20 +0200

csiph-web