On 2015-11-14 08:17, Ryan Schmidt wrote:
> port_portname wouldn't help with short port names like e, q and R,
> because it would also find tickets about ports whose names begin with
> e, q and R. Granted, what we have in Trac doesn't make it easy to
> find tickets about those ports either, especial
On Nov 13, 2015, at 1:16 PM, Arno Hautala wrote:
> On Fri, Nov 13, 2015 at 12:31 PM, Rainer Müller wrote:
>
>> Maybe it would be enough to search in the subject instead, but for some ports
>> with generic names this would return many unrelated results.
>
> It's less than ideal, but a conventio
Yes, this is a pet peeve of mine. Try figuring out whether a ticket has
been filed against the port "R" or not... It would be helpful to give the
option in this context not to use regexes, so to check whether the port
field is exactly "R" (or if separated into comma-delimited fields, one is
exactly
On Fri, Nov 13, 2015 at 12:31 PM, Rainer Müller wrote:
>
> Maybe it would be enough to search in the subject instead, but for some ports
> with generic names this would return many unrelated results.
It's less than ideal, but a convention of something like port_portname
would work for narrowing d
On 11/13/2015 03:54 PM, Ryan Schmidt wrote:
>
> On Nov 13, 2015, at 5:40 AM, Rainer Müller wrote:
>
>> Our Trac has some customizations (e.g. the port field and CC button), but
>> we always wanted more. The maintainer should automatically be notified when
>> the port field is set, tickets should
On Nov 13, 2015, at 5:40 AM, Rainer Müller wrote:
> Our Trac has some customizations (e.g. the port field and CC button), but we
> always wanted more. The maintainer should automatically be notified when the
> port field is set, tickets should be closed when a commit messages contains a
> "closes
On 11/12/2015 11:25 PM, Clemens Lang wrote:
> - On 12 Nov, 2015, at 19:48, Sean Farley s...@macports.org wrote:
>
>> Sure, it could include Jira, HipChat, and Bamboo, if you want. I only
>> said 'lost cause' because GitHub is so popular for open source projects.
>
> I don't think we would hav
Hi,
- On 13 Nov, 2015, at 08:39, Mojca Miklavec mo...@macports.org wrote:
> I can check the list of names against mine. It's weird that you had to
> manually add some names to it.
I looked at the history and found a couple of commits that were done using
local accounts, done by root, or done
On Thu, Nov 12, 2015 at 1:34 PM, Clemens Lang wrote:
> Hi Mojca,
>
> - On 12 Nov, 2015, at 10:04, Mojca Miklavec mo...@macports.org wrote:
>
>> Clemens, are you willing to set up some (temporary) repository with
>> regular updates, even if it's not perfect yet, just so that we can
>> follow the
Clemens Lang writes:
> Hi,
>
> - On 12 Nov, 2015, at 19:48, Sean Farley s...@macports.org wrote:
>
>> Sure, it could include Jira, HipChat, and Bamboo, if you want. I only
>> said 'lost cause' because GitHub is so popular for open source projects.
>
> I don't think we would have a use case f
Hi,
- On 12 Nov, 2015, at 19:48, Sean Farley s...@macports.org wrote:
> Sure, it could include Jira, HipChat, and Bamboo, if you want. I only
> said 'lost cause' because GitHub is so popular for open source projects.
I don't think we would have a use case for HipChat, but I like Jira (even
t
Ryan Schmidt writes:
> On Nov 12, 2015, at 3:04 AM, Mojca Miklavec wrote:
>> On Wed, Nov 11, 2015 at 11:37 AM, Ryan Schmidt wrote:
>>> On Nov 10, 2015, at 10:57 PM, Mojca Miklavec wrote:
At the moment it's the lack of Trac's functionality to browse the tree
and the logs that has
Hi Mojca,
- On 12 Nov, 2015, at 10:04, Mojca Miklavec mo...@macports.org wrote:
> Clemens, are you willing to set up some (temporary) repository with
> regular updates, even if it's not perfect yet, just so that we can
> follow the changes? (I can offer to run a script for incremental
> updat
On Nov 12, 2015, at 3:43 AM, Ryan Schmidt wrote:
> A seventh VM has been requested for El Capitan and I've been told that should
> be a resource problem, it's just a matter of setting it up, which will happen
> soon.
Correction: that should *not* be a resource problem.
On Nov 12, 2015, at 3:04 AM, Mojca Miklavec wrote:
> On Wed, Nov 11, 2015 at 11:37 AM, Ryan Schmidt wrote:
>> On Nov 10, 2015, at 10:57 PM, Mojca Miklavec wrote:
>>>
>>> At the moment it's the lack of Trac's functionality to browse the tree
>>> and the logs that has triggered the "demand" for thi
On Wed, Nov 11, 2015 at 11:37 AM, Ryan Schmidt wrote:
> On Nov 10, 2015, at 10:57 PM, Mojca Miklavec wrote:
>>
>> At the moment it's the lack of Trac's functionality to browse the tree
>> and the logs that has triggered the "demand" for this.
>
> That will get fixed. In asking about github, we're j
Clemens Lang writes:
> Hi,
>
> - On 11 Nov, 2015, at 11:03, Rainer Müller rai...@macports.org wrote:
>
>> On 2015-11-11 05:57, Mojca Miklavec wrote:
>>> Is there any chance that we put mirrors of the SVN repository there?
>>>
>>> I would suggest to use these for simplicity:
>>> https://
Hi,
- On 11 Nov, 2015, at 11:03, Rainer Müller rai...@macports.org wrote:
> On 2015-11-11 05:57, Mojca Miklavec wrote:
>> Is there any chance that we put mirrors of the SVN repository there?
>>
>> I would suggest to use these for simplicity:
>> https://www.macosforge.org/post/git-mirrors
On Nov 10, 2015, at 10:57 PM, Mojca Miklavec wrote:
>
> On Wed, Nov 11, 2015 at 12:58 AM, Lawrence Velázquez wrote:
>> On Nov 9, 2015, at 4:45 PM, Rainer Müller wrote:
>>
>>> On 2015-11-09 21:01, Mojca Miklavec wrote:
Does anyone know who owns
https://github.com/MacPorts
?
>>>
>
On 2015-11-11 05:57, Mojca Miklavec wrote:
> On Wed, Nov 11, 2015 at 12:58 AM, Lawrence Velázquez wrote:
>> Surprise! It's me.
>
> Great.
Good to know! I am glad we found you. :-)
> Is there any chance that we put mirrors of the SVN repository there?
>
> I would suggest to use these for simplic
> On Nov 10, 2015, at 15:58, Lawrence Velázquez wrote:
>
> On Nov 9, 2015, at 4:45 PM, Rainer Müller wrote:
>
>> On 2015-11-09 21:01, Mojca Miklavec wrote:
>>> Does anyone know who owns
>>> https://github.com/MacPorts
>>> ?
>>
>> I would be interested to know that as well. I actually found
Feels like MacOSForge is circling the drain. XQuartz left. Now we're having
nothing but trouble.
—Mark
___
Mark E. Anderson
On Tue, Nov 10, 2015 at 11:57 PM, Mojca Miklavec wrote:
> On Wed, Nov 11, 2015 at 12:58 AM, Lawrence Velázquez wrote:
> > On Nov 9, 2015, at 4:45 PM,
On Wed, Nov 11, 2015 at 12:58 AM, Lawrence Velázquez wrote:
> On Nov 9, 2015, at 4:45 PM, Rainer Müller wrote:
>
>> On 2015-11-09 21:01, Mojca Miklavec wrote:
>>> Does anyone know who owns
>>>https://github.com/MacPorts
>>> ?
>>
>> I would be interested to know that as well. I actually found a
On Nov 9, 2015, at 4:45 PM, Rainer Müller wrote:
> On 2015-11-09 21:01, Mojca Miklavec wrote:
>> Does anyone know who owns
>>https://github.com/MacPorts
>> ?
>
> I would be interested to know that as well. I actually found a way to
> send them a message last week. Now we can just wait for th
On 2015-11-09 21:01, Mojca Miklavec wrote:
> Does anyone know who owns
> https://github.com/MacPorts
> ?
I would be interested to know that as well. I actually found a way to
send them a message last week. Now we can just wait for them to get back
to us.
Rainer
___
Does anyone know who owns
https://github.com/MacPorts
?
Thank you,
Mojca
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
26 matches
Mail list logo
