Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8188
| From | Nikolaus Rath <Nikolaus@rath.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | How to put experimental upload into git |
| Date | 2016-02-01 17:20 +0100 |
| Message-ID | <qXpmO-5sL-23@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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
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