3 ms·
I'm doing that successfully for years. But I added more: https://github.com/perl11/cperl/blob/master/pod/perlcperl.pod https://github.com/perl11/cperl/blob/mast
by rurban 7y ago
I'm doing that successfully for years. But I added more: https://github.com/perl11/cperl/blob/master/pod/perlcperl.pod https://github.com/perl11/cperl/blob/master/pod/perlcperl.po...
The .git/cache is a submodule, so others can easily rebase also. And a lot of helper scripts to rebase and pull --rebase all work branches automatically. All current branches are constantly rebased to master, others default to pull --rebase (aliased to lb), with the shared. git/cache there are no conflicts for years.
I'm also doing this for several forks automatically, like adding patches and CI smokes to popular repos like clisp, libffi, openssl, pcre2, coreutils and many more. These are rebased hourly, conflicts appear maybe once a year.