Sorry, my firefox os email client swallowed the contents of my previous
mail, it seems :(
Switching back to turbolinks in buster would be just a matter of
changing watch file and removing copy-gemspec file. Maintaining a patch
is comparatively more work for the same result, but I will do it anyway
Antonio Terceiro wrote:
> On Sun, Jan 15, 2017 at 10:03:40PM +0530, Pirate Praveen wrote:>> On ഞായര്
> 15 ജനുവരി 2017 09:42 വൈകു, Antonio Terceiro wrote:>>> 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 for
On Sun, Jan 15, 2017 at 10:03:40PM +0530, Pirate Praveen wrote:
> On ഞായര് 15 ജനുവരി 2017 09:42 വൈകു, Antonio Terceiro wrote:
> > 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?
> >
>
>
On ഞായര് 15 ജനുവരി 2017 09:42 വൈകു, Antonio Terceiro wrote:
> 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?
>
Its basically backported changes from newer releases to 2.5 version.
From RE
On Sun, Jan 15, 2017 at 02:29:40PM -, 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 m
5 matches
Mail list logo
