On 19/01/07, via RT James Bence <[EMAIL PROTECTED]> wrote:
# New Ticket Created by "James Bence"
# Please include the string: [perl #41292]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41292 >
The test t/codingstd/trailin
Paul, did you mean to update all these tcl files with your patch with
no commit message?
If not, this isn't the first time you've reverted code elsewhere in
the repository when doing your manual merges... (and it affected tcl
last time, too.) - Please fix them.
If so, please use *real* co
Will,
I'm really deeply sorry for reverting stuff with my last commit. It's
definitely not what I intended. I didn't even edit the tcl (and
other) files, which is what is totally weird. I wanted to commit a
line endings change to shootout.t in lua, but when I went 'svk push' I
got an "Empty co
On Friday 19 January 2007 04:46, Paul Cochrane wrote:
> I wanted to commit a
> line endings change to shootout.t in lua, but when I went 'svk push' I
> got an "Empty commit message" error again and the only way I know to
> fix this is to use 'svk merge -c //parrot/local/
> //parrot/remote -m "a n
On 1/19/07, chromatic <[EMAIL PROTECTED]> wrote:
On Friday 19 January 2007 04:46, Paul Cochrane wrote:
> I wanted to commit a
> line endings change to shootout.t in lua, but when I went 'svk push' I
> got an "Empty commit message" error again and the only way I know to
> fix this is to use 'svk
> I wanted to commit a
> line endings change to shootout.t in lua, but when I went 'svk push' I
> got an "Empty commit message" error again and the only way I know to
> fix this is to use 'svk merge -c //parrot/local/
> //parrot/remote -m "a non-empty commit message"', then it seems to
> commit e
On 19/01/07, jerry gay <[EMAIL PROTECTED]> wrote:
On 1/19/07, chromatic <[EMAIL PROTECTED]> wrote:
> On Friday 19 January 2007 04:46, Paul Cochrane wrote:
>
> > I wanted to commit a
> > line endings change to shootout.t in lua, but when I went 'svk push' I
> > got an "Empty commit message" error
Paul Cochrane wrote:
Essentially you should svk pull before any commit or push operation,
which helps avoid having to do conflict resolution.
I'm adding in spots in all caps where you should do a svk pull.
Kevin
I'm working from a mirrored copy, and my usual work cycle is:
svk up -sm looks
Hi @larry,
I want to remember to my proposal from september 2006.
It targets on changing S04. The discussion is summarized on:
http://www.oreillynet.com/onlamp/blog/2006/09/weekly_perl_6_mailing_list_sum_3.html
So, please change S04 as discussed.
Thanks
Stefan
-
On Jan 19, 2007, at 7:46 AM, Paul Cochrane wrote:
Will,
I'm really deeply sorry for reverting stuff with my last commit.
Heh. Things happen. It's ok. Jerry did worse to tcl just before the
release. =-)
I appreciate the fix up. I was a certainly a little grumpy, but it's
fixed, before I
as chromatic hints at here, you should make sure you have the latest
SVN::Mirror. i know we've seen problems with svk in the past with
empty commit messages, and this was (part of)? the solution.
It seems I had two versions of SVN::Mirror floating around. Version
0.72 (the latest) was in /usr/li
Author: larry
Date: Fri Jan 19 17:48:06 2007
New Revision: 13530
Modified:
doc/trunk/design/syn/S05.pod
Log:
Further attempts to make default auto-tokening rules unsurprising.
Modified: doc/trunk/design/syn/S05.pod
=
Author: chromatic
Date: Fri Jan 19 22:22:49 2007
New Revision: 16709
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
trunk/src/pmc/namespace.pmc
trunk/t/pmc/namespace.t
Log:
Added add_namespace() method t
Author: chromatic
Date: Fri Jan 19 22:23:17 2007
New Revision: 16712
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
trunk/src/pmc/namespace.pmc
trunk/t/pmc/namespace.t
Log:
Added del_namespace() method t
Will Coleda wrote:
While it would be possible to implement
the basic functionality by wrapping existing subs in other subs,
I'm not sure that would help with
[trace info], which provides a way to report on all the traces that are
currently set.
Isn't that more a matter of setting a flag on the
On 1/19/07, Allison Randal <[EMAIL PROTECTED]> wrote:
(That also means you can monkey around with the args before passing them
on to the wrapped sub.)
- It should be possible both to put multiple wrappers/traces on a
subroutine, and to put wrappers around other wrappers. So these are all
possib
16 matches
Mail list logo
