On Wed, Apr 14, 2021 at 04:19:29PM +0100, Daniel P. Berrangé wrote: > One example approach to source-git I've used... > > Rather than having source-git branch names matching dist-git, > use a different naming convention that is based off the upstream > version primarily. > > eg if upstream has v1.0 and v1.2 tags, I might have a 'v1.0-f33' > branch, and if I rebase Fedora to v1.2, then I'd just switch to > using a v1.2-f33 branch instead. The v1.0-f33 history remains > intact forever, no force push required to rebase to new version. As a concrete example, this is how the Fedora OCaml repo works (with a different naming convention): https://pagure.io/fedora-ocaml/branches?branchname=master Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
