Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8188 > unrolled thread
| Started by | Nikolaus Rath <Nikolaus@rath.org> |
|---|---|
| First post | 2016-02-01 17:20 +0100 |
| Last post | 2016-02-02 05:50 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.maint.python
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
| From | Nikolaus Rath <Nikolaus@rath.org> |
|---|---|
| Date | 2016-02-01 17:20 +0100 |
| Subject | How to put experimental upload into git |
| Message-ID | <qXpmO-5sL-23@gated-at.bofh.it> |
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.«
[toc] | [next] | [standalone]
| From | Barry Warsaw <barry@debian.org> |
|---|---|
| Date | 2016-02-01 18:00 +0100 |
| Message-ID | <qXpZw-5Jg-9@gated-at.bofh.it> |
| In reply to | #8188 |
On Feb 01, 2016, at 08:10 AM, Nikolaus Rath wrote: >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. I haven't done this specifically, but I have used branches w/git-dpm. I can't say if been particularly successful at it for more complex (long-running) cases. But your case sounds relatively simple so I'd probably do what you suggest above. Cheers, -Barry
[toc] | [prev] | [next] | [standalone]
| From | Stefano Rivera <stefanor@debian.org> |
|---|---|
| Date | 2016-02-02 05:50 +0100 |
| Message-ID | <qXB4C-5tc-3@gated-at.bofh.it> |
| In reply to | #8188 |
Hi Nikolaus (2016.02.01_18:10:28_+0200) > I'd like to upload the newest python-llfuse release to experimental first. > > * Commit regularly, with the upload to unstable becoming a descendant of > the upload to experimental. I think it's perfectly reasonable to have experimental uploads like this in master. If you need to do another unstable upload that precedes it (which seems rare in these cases), you can always go back and start a diverging branch. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web