On Sun, Jan 15, 2017 at 02:29:40PM -0000, Pirate Praveen wrote: > Hi, > > I'm planning to update gitlab to latest patch release 8.13.11 and > it needs gitlab-turbolinks-classic, which is a fork of > turbolinks. I'm planning to switch to gitlab's fork for > ruby-turbolinks package. I have already made the changes locally > and autopkgtest for rails is successful (I'm providing gemspec > files for both). I don't see much issues with the switch but just > asking for second opinion before actual upload. I plan to upload > it in next two days if there is no objection or before that if > there is support for the move.
I would prefer to not do that this close to a freeze. Is there a good reason for the fork? What are the differences between the fork and the original?
signature.asc
Description: PGP signature
