> Just my 2-cents
>
> IF it isn't BROKEN....please DON'T fix it.
the question here is: how much time coders (maintainers, contributors,
and users) would spare if the administration was shifted to a
different infrastructure.
i cannot grow to like git (i still prefer darcs), but github simply
provides so many extra goodies around git, and with such a smooth
learning curve, that i think it's very much worth taking that road.
i think it'd also be worth having a separate kernel fork (repo) as
a git submodule under the openwrt git repo. it could have branches for
the corresponding openwrt branches, and with its separate commit
history it would make comparison with the mainline kernel way much
simpler than it is today.
potentially the same for some other projects as well, e.g. the
toolchain repos?
> Regarding downstream forks, would using Git also make it easier for
> people like project turris to push appropriate changes back into
> OpenWrt proper?
git checkout -b fixing-this-and-that
gitk [and cherrypick or tailor the branch with the gui as needed]
git push
go to github.com and create a pull request
the whole process can be shorter than 5 minutes, and after that anyone
can go and browse it among the open pull requests.
some more 0.02,
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Justice is not concerned with the results of the various
transactions, but only with whether the transactions themselves are
fair.”
— F.A. Hayek (1899–1992), 'Law, Legislation and Liberty', I.6.j
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
