Switching to gitlab-turbolinks-classic (gitlab fork) for ruby-turbolinks source
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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.
Thanks
Praveen
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlh7h08ACgkQzh+cZ0US
wiq88Q//YRlpR8wbOJA+viwls9IMU8B3Rl/WLeDodRJyhvGmLoJik/idB2N+VT56
hzcd5uTfI3TQ8v4CfV3VCMTA8fjJIkyN4Pwnlg6WlXO3d06feebdhje95+ZV1Hi4
qx7wDSQ27Cd+DMpXy3tk21URwi/19gU309faiVWc8CCy7oFSpRViyqMtbALFI5QV
UKsfpbsoFYThDotR0AbJVXIlBc5yXkzIn1bC1e1AD4T9zBGTgg42DR6+qpPQ2yCB
qtE5HYLtJSbO9Vx5LXDhlqiPyx2D7LAUN7I7LUBbBP9FHA8ooVs4l6MVgiQWRxIg
VdKBSbD4Cy3FSFJ+xR8pRJwwlCjSdPHGOodyX7iIQTQ+9VmYoi1tJ/zUNNR4pZoy
SLSqZMVjJbrYDHbLDohVePgQ1ZKuYFTpntyxJwQ7wXxEeSgcEp7GqzFiXhAKEGj2
uiEu8QVCj9jPXvn/DNCaCWPd7LW7aMs/RaG81P86RuS4d7r10wSSoa/0ucm+XOiO
nZ8YAGKEl/sy1mYHgTkOaL4SqpBZBZF5pTsy8FdDVCn5VXMzcf+jNZkINVi9K92m
BD4sGihpWtsS+sWpnf7tMDo2m0wmI5i+SUNUxF/sP3i4fHkQBPKlwD02Li0+dEPy
j1fKCXZvspjsZ2Zhe3uQOyqnKjCWGX/dOilJOW1yv7HdwTlrQ7A=
=gUJm
-----END PGP SIGNATURE-----
Reply to: