Thanks for coding this, s2software!

While we’re transitioning to a new integrated tracker, could you report the issue on our current main tracker at JoomlaCode and cross-reference each with a link to the other? Here’s the process for reporting on the other tracker:
http://docs.joomla.org/Filing_bugs_and_issues

Alternatively, let me know if you’d like me to create it for you and I can go ahead and do that.

Thanks in advance and thanks again for coding this, s2software!

Hi Nick.
If it's not a problem, I accept your offer in creating it for me.
Thanks for your help.

Regards,
Stefano Storti

Il 08/05/2013 06:28, Nick Savov ha scritto:

Thanks for coding this, s2software!

While we’re transitioning to a new integrated tracker, could you
report the issue on our current main tracker at JoomlaCode and
cross-reference each with a link to the other? Here’s the process for
reporting on the other tracker:
http://docs.joomla.org/Filing_bugs_and_issues

Alternatively, let me know if you’d like me to create it for you and I
can go ahead and do that.

Thanks in advance and thanks again for coding this, s2software!

—
Reply to this email directly or view it on GitHub
#1113 (comment).

Hi @s2software

Could you update this to the latest master? It can get tested during our PBF event.

I merged current master to the patch branch. Then I tried to make a new pull request but github says there's not differences. Is seems that this pull request has been already merged in the master.

The patch could not be applied because the repository is missing

@s2software Can you try to redo that PR? GitHub says the source repo is missing and also the PR is targeted against our master branch. It should be against our staging branch instead.

I'm closing this PR and hope you create a new one which then works. Thanks!