Re: [perl6/specs] 761178: remove some some duplicate words words

2010-09-08 Thread Jan Ingvoldstad
On Wed, Sep 8, 2010 at 07:41, Jason Switzer  wrote:

>
> I'm surprised anyone actually ever read the diff part of the message. I
> would prefer to never see that feature again. This has a link to the
> commit,
> which has a much better diff viewer than plaintext email (hello? 1997
> called, they want their change notices back).


In some respects, I want 1997 back, since people learned how to work
efficiently rather than not. ;)

I both like and can read the contextual diffs just fine.


> It links to the actual change
> and even highlights the changes.


Yes, it's all very nice, and nothing that needs to go away. Having it both
ways can't hurt.


> Now I'll actually take a moment to sift
> through the changes. I vote to never see those diff emails ever again. In
> fact, if the diffs are brought back, I'll just subscribe to the commit feed
> and skip the email notice all together.
>
> That seems like a reasonable solution for you, then.
-- 
Jan


[perl6/specs] 692474: [S03] Attempt bring more clarity to the semantics ...

2010-09-08 Thread noreply
Branch: refs/heads/master
Home:   http://github.com/perl6/specs

Commit: 692474967ab8535f370d859488da592555e17d8d

http://github.com/perl6/specs/commit/692474967ab8535f370d859488da592555e17d8d
Author: TimToady 
Date:   2010-09-07 (Tue, 07 Sep 2010)

Changed paths:
  M S03-operators.pod

Log Message:
---
[S03] Attempt bring more clarity to the semantics of series operators.
The limit is now always a smartmatch, which must match exactly.
No attempt is made to intuit which direction the series is going,
or to turn exact matches into inequalities.  Non-numeric series
behavior is regularized to work like single characters, taking
into account the target value as indicative of the range desired.
The old semantics are relegated to explicit *.succ and limits.
Also, ... and ...^ are defined in terms of last($x) vs last().




perl6-language@perl.org

2010-09-08 Thread noreply
Branch: refs/heads/master
Home:   http://github.com/perl6/specs

Commit: 08f22a7b7e0e9f5cc54efccd5f7fd54a35f681e4

http://github.com/perl6/specs/commit/08f22a7b7e0e9f5cc54efccd5f7fd54a35f681e4
Author: Kodi Arfer 
Date:   2010-09-07 (Tue, 07 Sep 2010)

Changed paths:
  M S04-control.pod

Log Message:
---
Changed some references to (the now nonexistent) &localtime to use &now instead.




[perl6/specs] 7e4097: [S09] too-long subscript range behaves differently...

2010-09-08 Thread noreply
Branch: refs/heads/master
Home:   http://github.com/perl6/specs

Commit: 7e409792fc638312b0b9c5f4ec8ee2954696f507

http://github.com/perl6/specs/commit/7e409792fc638312b0b9c5f4ec8ee2954696f507
Author: TimToady 
Date:   2010-09-07 (Tue, 07 Sep 2010)

Changed paths:
  M S09-data.pod

Log Message:
---
[S09] too-long subscript range behaves differently as rvalue or lvalue




Re: [perl6/specs] 761178: remove some some duplicate words words

2010-09-08 Thread Richard Hainsworth
I do want the diffs back: its the only way I have to keep at least some 
idea of what is changing any why.


Dont care if I'm called an old foggy either - 1997 wasnt that long ago 
for me.


On 09/08/10 13:32, Jan Ingvoldstad wrote:

On Wed, Sep 8, 2010 at 07:41, Jason Switzer  wrote:

   

I'm surprised anyone actually ever read the diff part of the message. I
would prefer to never see that feature again. This has a link to the
commit,
which has a much better diff viewer than plaintext email (hello? 1997
called, they want their change notices back).
 


In some respects, I want 1997 back, since people learned how to work
efficiently rather than not. ;)

I both like and can read the contextual diffs just fine.


   

It links to the actual change
and even highlights the changes.
 


Yes, it's all very nice, and nothing that needs to go away. Having it both
ways can't hurt.


   

Now I'll actually take a moment to sift
through the changes. I vote to never see those diff emails ever again. In
fact, if the diffs are brought back, I'll just subscribe to the commit feed
and skip the email notice all together.

That seems like a reasonable solution for you, then.
 


Re: [perl6/specs] 761178: remove some some duplicate words words

2010-09-08 Thread Darren Duncan

Jason Switzer wrote:

On Tue, Sep 7, 2010 at 11:29 AM, Moritz Lenz  wrote:


Brandon S Allbery KF8NH wrote:

On 9/7/10 08:17 , nore...@github.com wrote:

Commit: 7611788411e5aff5f3ae150e2da9929ee546d6d8


http://github.com/perl6/specs/commit/7611788411e5aff5f3ae150e2da9929ee546d6d8

It was nicer when these contained the actual diffs like they used to,
instead of forcing me to go poke at the tree.

Indeed. Any contributions to restoring that behavior are very welcome.


I'm surprised anyone actually ever read the diff part of the message. I
would prefer to never see that feature again. This has a link to the commit,
which has a much better diff viewer than plaintext email (hello? 1997
called, they want their change notices back). It links to the actual change
and even highlights the changes. Now I'll actually take a moment to sift
through the changes. I vote to never see those diff emails ever again. In
fact, if the diffs are brought back, I'll just subscribe to the commit feed
and skip the email notice all together.


I like the email diffs and think that both they plus the link to the web diff 
should be in the emails.


Sure, the web page diffs are prettier, but the email diffs are much more 
convenient, and pretty enough.  With the email we don't have to click a link to 
see what changed.


And particularly important, if we want to reply with a *comment* on the diff, it 
is easy to cite the portions we're commenting on, because a simple reply on the 
list message has the diffs quoted.


-- Darren Duncan


Re: [perl6/specs] 761178: remove some some duplicate words words

2010-09-08 Thread Patrick R. Michaud
On Wed, Sep 08, 2010 at 04:02:10PM +0400, Richard Hainsworth wrote:
> I do want the diffs back: its the only way I have to keep at least
> some idea of what is changing any why.

We know that a lot of people would like to see the diffs available
through the commit messages, but afaik none of us actively maintaining
the github archive quite know how to make that happen.  Something
beyond "please bring diffs back" would be very helpful to us here.

For those who prefer to just have links to the diffs without the
text of the diffs, subscribing to the commit RSS feed is probably 
the best bet.

Pm


Re: [perl6/specs] 761178: remove some some duplicate words words

2010-09-08 Thread Moritz Lenz
Patrick R. Michaud wrote:
> On Wed, Sep 08, 2010 at 04:02:10PM +0400, Richard Hainsworth wrote:
>> I do want the diffs back: its the only way I have to keep at least
>> some idea of what is changing any why.
> 
> We know that a lot of people would like to see the diffs available
> through the commit messages, but afaik none of us actively maintaining
> the github archive quite know how to make that happen.  Something
> beyond "please bring diffs back" would be very helpful to us here.

Currently the "Email" service hook in github is enabled for the specs repo.

They are open source, see http://github.com/github/github-services for
details. Somebody could implement the include-the-diff feature, and make
the github folks apply the changes.

Or somebody could follow the feed and send emails to p6l, in which case
I'd disable the service hook.

Cheers,
Moritz