Re: Survey: git packaging practices / repository format
- To: debian-devel@lists.debian.org
- Subject: Re: Survey: git packaging practices / repository format
- From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
- Date: Mon, 1 Jul 2019 15:14:49 +0200
- Message-id: <[🔎] 464ef85a-12d0-6159-70fe-e98499c65524@metux.net>
- In-reply-to: <87k1e9szye.fsf@tethera.net>
- References: <23789.22766.778482.983490@chiark.greenend.org.uk> <8736kxvaib.fsf@tethera.net> <23790.61056.550615.867739@chiark.greenend.org.uk> <23790.61331.497175.309271@chiark.greenend.org.uk> <87k1e9szye.fsf@tethera.net>
On 29.05.19 23:39, David Bremner wrote:
>> Also, how do you move to a new upstream version ?
>
> use git merge, typically from an upstream tag, or from a debian specific
> upstream branch with tarballs imported on top of upstream history.
Uh, that creates an pretty ugly, unreadable git repo and makes
interacting w/ upstream (eg. submitting patches) unncessarily hard.
That's something I regularily see w/ crappy vendor kernels, which then
take lots of time to bring them into some somewhat usable state :o
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
Reply to: