On 2 December 2016 at 14:55, Rainer Müller wrote:
> On 2016-12-02 12:28, Mojca Miklavec wrote:
>
>> But there might be some issues. Looking at a random commit email:
>>
>> https://lists.macports.org/pipermail/macports-changes/2016-December/144725.html
>> saying
>>An HTML attachment was scru
> On Dec 2, 2016, at 8:47 PM, Joshua Root wrote:
>
>> On 2016-12-3 02:45, René J.V. Bertin wrote:
>>
>> Hi,
>>
>> I'm trying to understand a regression that seems coupled to the
>> 2.3.4 -> 2.3.5 upgrade (or more exactly, "master just after 2.3.4"
>> -> "master 25 commits after 2.3.5").
>>
>>
On 2016-12-3 02:45 , René J.V. Bertin wrote:
Hi,
I'm trying to understand a regression that seems coupled to the 2.3.4 -> 2.3.5 upgrade (or more
exactly, "master just after 2.3.4" -> "master 25 commits after 2.3.5").
I had
{{{
proc macports::normalize { filename } {
set nprefix [file dirn
On Friday December 02 2016 21:52:00 Rainer Müller wrote:
> should review and acknowledge the merge. In any case, the maintainer
> needs to be notified, which can only be achieved with an @ mention.
OK, I guess that answers my question.
R.
On 2016-12-02 21:47, René J.V. Bertin wrote:
> On Friday December 02 2016 20:54:41 Rainer Müller wrote:
>
>> Which notification mail? There are no notification mails going to the
>> maintainer for pull requests unless the person opening the pull requests
>
> We must be talking about different thi
On Friday December 02 2016 20:54:41 Rainer Müller wrote:
> Which notification mail? There are no notification mails going to the
> maintainer for pull requests unless the person opening the pull requests
We must be talking about different things.
If the maintainer opens the PR and he hasn't disab
On 2016-12-02 20:39, René J.V. Bertin wrote:
> What does "@mentioning maintainers on pull requests" do, concretely?
> (If it's akin to those #sillytweetythingies, aka "hey @RJVB, could you ..." -
> that looks just as silly to me, if you read the notification emails before
> opening the webpage :
On Friday December 02 2016 10:49:17 Mojca Miklavec wrote:
> https://trac.macports.org/ticket/52928
> We need emails for reaching maintainers and sending emails from the buildbot,
> but we also want to be able to `@mention` maintainers on pull requests.
> Alternatively we could have a plain text
Hi,
I'm trying to understand a regression that seems coupled to the 2.3.4 -> 2.3.5
upgrade (or more exactly, "master just after 2.3.4" -> "master 25 commits after
2.3.5").
I had
{{{
proc macports::normalize { filename } {
set nprefix [file dirname [file normalize "${macports::prefix}/foo"]
> On Dec 2, 2016, at 4:09 AM, Joshua Root wrote:
>
> Joshua Root (jmroot) pushed a commit to branch master
> in repository macports-contrib.
>
>
> https://github.com/macports/macports-contrib/commit/03f312cb5470db0f189df70cdc2070875279efad
>
> The following commit(s) were added to refs/heads/
On 2016-12-02 12:28, Mojca Miklavec wrote:
> On 2 December 2016 at 12:13, Zero King wrote:
>> I didn't write to that list, my commit was merged into master and so I've
>> got this mail.
>
> In that case it's a problem with our scripts or mailman configuration
> and Rainer should be able to answer
On 2 December 2016 at 12:13, Zero King wrote:
> I didn't write to that list, my commit was merged into master and so I've
> got this mail.
In that case it's a problem with our scripts or mailman configuration
and Rainer should be able to answer you.
I guess that the idea was to use the committer
I didn't write to that list, my commit was merged into master and so
I've got this mail.
On 12/2/16 11:07 AM, Mojca Miklavec wrote:
On 2 December 2016 at 12:02, Zero King wrote:
I don't want to receive such mail but would prefer not to subscribe to the
macports-changes list either. What shou
On 2 December 2016 at 12:02, Zero King wrote:
>
> I don't want to receive such mail but would prefer not to subscribe to the
> macports-changes list either. What should I do?
>From the technical point of view you can easily subscribe and mark
that you don't want to receive any emails. Then your p
I don't want to receive such mail but would prefer not to subscribe to
the macports-changes list either. What should I do?
Forwarded Message
Subject:Your message to macports-changes awaits moderator approval
Date: Fri, 02 Dec 2016 11:50:39 +0100
From: macports-cha
Hi,
A while back someone (or 2 someones) on here went ahead and implemented ideas I
raised:
- `port environment` to dump an overview of the environment and context used
when running Portfiles (not exactly what I was looking for but still useful
from time to time)
- a more generalised `port in
16 matches
Mail list logo
