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

How to put experimental upload into git

Path	csiph.com!feeder.erje.net!1.us.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Nikolaus Rath <Nikolaus@rath.org>
Newsgroups	linux.debian.maint.python
Subject	How to put experimental upload into git
Date	Mon, 01 Feb 2016 17:20:02 +0100
Message-ID	<qXpmO-5sL-23@gated-at.bofh.it> (permalink)
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Mon Feb 1 16:10:47 2016
Old-Return-Path	<Nikolaus@rath.org>
X-Amavis-Spam-Status	No, score=-2.6 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FOURLA=0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no autolearn_force=no
X-Policyd-Weight	DYN_NJABL=SKIP(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .rath. - helo: .out5-smtp.messagingengine. - helo-domain: .messagingengine.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7
Dkim-Signature	v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=Xp5uZKSR65yq9vKQ91EPI/BWIOE=; b=jzMRH yIA7P7q4TyjIvzUsdZ0FOWHrJymdRxdspDfk9cQGJcTMs07yioW1uuDKO5MmAcP0 hEGd11i/M+ZQlnPiMp9OXIjzuqTblrZz4NQ0azV78B/D2DeTItVelEhZQe4OyJIF n5F1GxruFJgVNS94wo/VSFn5xUHTlardmqqdEE=
X-Sasl-Enc	CD3PDZF/EqfBLth54Bk4LVK/irQd8mRjGi+B3uHBj5hK 1454343029
Mail-Copies-To	never
Mail-Followup-To	debian-python@lists.debian.org
User-Agent	Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.4 (gnu/linux)
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding	quoted-printable
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/13512
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/8760y8mmx7.fsf@thinkpad.rath.org
Approved	robomod@news.nic.it
Lines	33
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Mon, 01 Feb 2016 08:10:28 -0800
X-Original-Message-ID	<8760y8mmx7.fsf@thinkpad.rath.org>
Xref	csiph.com linux.debian.maint.python:8188

Show key headers only | View raw

Hello,

I'd like to upload the newest python-llfuse release to 
experimental first.

Are there any best practices for handling this on the git side? I 
could imagine:

 * Don't commit anything to git at all (it would only be a single 
 commit 
   for the upload), commit when uploading to unstable.

 * Commit regularly, with the upload to unstable becoming a 
 descendant 
   of the upload to experimental.

 * Commit to a new branch that then becomes dangling, because the 
 next 
   upload to unstable descends from the most-recent unstable 
   upload rather than from experimental.

Thoughts?

Thanks,
-Nikolaus
 
(No Cc on replies please, I'm reading the list)
-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

How to put experimental upload into git Nikolaus Rath <Nikolaus@rath.org> - 2016-02-01 17:20 +0100
  Re: How to put experimental upload into git Barry Warsaw <barry@debian.org> - 2016-02-01 18:00 +0100
  Re: How to put experimental upload into git Stefano Rivera <stefanor@debian.org> - 2016-02-02 05:50 +0100

csiph-web