its true trac has never done this, so its not a recent change.
Though if the new "Cc me" button were any smaller, it would be considered
a web bug. :-)
Fred Wright
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
the changes are only in the working
directory. It's not clear whether doing this with or without the reset is
better as an "svn analogy", given that svn doesn't have an index.
Fred Wright
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
e() is available, or whether to provide a
replacement. Making that work properly is better than just commenting out
the colliding typedef.
Fred Wright
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
ow if this works across all OS versions.
Hiding the macports directory also gets in the way of attaching build logs
to tickets, since the browser's dialog box can't navigate to them. I've
unhid this directory in the past for that reason, but every so often
something "fixes"
keep branches inherited from upstream
"pristine", i.e. fast-forwardable. That's less of an issue for someone
with direct commit access, though even there, working in a branch and
merging separately reduces the collision window for pushes.
Fred Wright
__
se should require any interactions
with taskgated, so any mention of taskgated tweaking should probably say
that it's only needed for *local* debugging.
At least the taskgated tweak doesn't open anywhere near as big a security
hole as what you need to do to run your own kexts on >=1
On Mon, 5 Sep 2016, Brandon Allbery wrote:
> On Mon, Sep 5, 2016 at 8:10 PM, Fred Wright wrote:
>
> > But when they switched to Intel, they also switched
> > to -O2. This allowed them to inflate the performance benefit of the
> > architecture switch. :-)
> >
n to a dull roar in relation to disk
drives at the time. But when they switched to Intel, they also switched
to -O2. This allowed them to inflate the performance benefit of the
architecture switch. :-)
Fred Wright
___
macports-dev mailing list
macpor
doesn't really simplify anything, so it's mainly
only useful in cases where the main repo isn't hosted on GitHub (and hence
where "fork" is meaningless).
BTW, it's worth mentioning that "fetch" doesn't touch the working
directory or index at all, so it can safely be done at any time. Then
after fetching, all the fetched commits are available locally for
examination, diffing, etc.
Fred Wright
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Sat, 13 Aug 2016, Christopher Jones wrote:
> > On 12 Aug 2016, at 11:30 pm, Fred Wright wrote:
> > On Fri, 12 Aug 2016, Chris Jones wrote:
> >> On 11/08/16 20:40, Fred Wright wrote:
> > [...]
> >>> Well, leaving something alone that's working jus
On Fri, 12 Aug 2016, Chris Jones wrote:
> On 11/08/16 20:40, Fred Wright wrote:
[...]
> > Well, leaving something alone that's working just fine is hardly much of a
> > maintenance burden.
>
> On the other hand, whats the rationale for keeping 2.6, given 2.7 is the
>
On Thu, 11 Aug 2016, Lawrence Velázquez wrote:
> > On Aug 11, 2016, at 3:40 PM, Fred Wright wrote:
> >
> > Well, leaving something alone that's working just fine is hardly much
> > of a maintenance burden.
>
> As Josh noted, this approach is fine for CPytho
On Wed, 10 Aug 2016, Lawrence Velázquez wrote:
> On Aug 10, 2016, at 5:21 PM, Fred Wright wrote:
>
> > I don't consider Python 2.6 to be "cruft". Developers need many
> > versions of Python installed for testing, and that includes any
> > packages that
create local versions of portfiles
solely to add versions that are missing for no substantive reason.
Python 2.6 here:
MacPro:~ fw$ port installed|egrep 'py(|thon)26'
py26-cairo @1.10.0_3 (active)
py26-pip @8.1.2_0 (active)
py26-readline @6.2.4.1_1 (active)
py26-setuptools @25.1.0_
ulnerabilities in OpenSSL have been found, all in
relation to the support for "export grade" keys.
Fred Wright
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Mon, 22 Feb 2016, Mojca Miklavec wrote:
> On 22 February 2016 at 01:56, Fred Wright wrote:
> > On Wed, 10 Feb 2016, Fred Wright wrote:
> >> On Sat, 6 Feb 2016, Fred Wright wrote:
> >>
> >> > It's been 3 weeks since I posted patches to update gpsd t
On Wed, 10 Feb 2016, Fred Wright wrote:
> On Sat, 6 Feb 2016, Fred Wright wrote:
>
> > It's been 3 weeks since I posted patches to update gpsd to 3.16 (ticket
> > #50288), fixing #47739 in the process.
Now 5 weeks. Although this got some attention, it's still in li
Resending after subscribing.
On Sat, 6 Feb 2016, Fred Wright wrote:
> It's been 3 weeks since I posted patches to update gpsd to 3.16 (ticket
> #50288), fixing #47739 in the process.
>
> Also, the obsolete update request for 3.15 (#50237) should be closed
18 matches
Mail list logo
