Re: Preferred git branch structure when upstream moves from tarballs to git
On Tue, Apr 30, 2019 at 09:04:09AM +0200, Thomas Goirand wrote:
> What I found the most easy way is to just use whatever branching names
> upstream is using, and *never* store them in Salsa. If you need upstream
> repository, you can simply run a ./debian/rules fetch-upstream-remote,
> and most of the time, the only thing you need, is merging a tag. What I
> push to Salsa are upstream tags only, which is enough.
Why? I strongly disagree: having the upstream tree in the same repo
as packaging is awesome. It lets you mix patches both ways with no effort.
Having the upstream tree at home but not pushing it deprives contributors
who are not you of this comfort.
As all the data is already in the repo, having it available as a branch
and tags doesn't cost any non-metadata space.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄⠀⠀⠀⠀
Reply to: