Hi,
On Mon, Sep 26, 2016 at 11:23:17AM -0700, Dan Ports wrote:
> For me, the main benefit is that it's immediately obvious where the
> patch comes from, and, since it's github, how it relates to the
> release version. (In this case, it's a backported patch from an
> unreleased version.)
This is s
On Mon, Sep 26, 2016 at 07:23:38PM +1000, Joshua Root wrote:
> I really don't see a problem with using patch_sites for any patches that are
> available for download somewhere stable. In fact it's even slightly
> preferable because it avoids the extra work of adding the file and adding a
> comment l
On 2016-9-26 18:18 , Ryan Schmidt wrote:
On Sep 24, 2016, at 8:57 PM, dpo...@macports.org wrote:
+# fix g_slice_set_config error (#52347)
+patch_sites https://github.com/libfuse/sshfs/commit/
+patchfiles-append e5acfce8eda218d.patch
We usually reserve the use of externally-hosted
> On Sep 24, 2016, at 8:57 PM, dpo...@macports.org wrote:
>
> Revision
> 153120
> Author
> dpo...@macports.org
> Date
> 2016-09-24 18:57:45 -0700 (Sat, 24 Sep 2016)
> Log Message
>
> sshfs: fix "GLib-CRITICAL **: g_slice_set_config: assertion failed" warning
> (#52347)
>
> Modified Paths
>
>
