> 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 even had a chance to sit back down and look at the
co
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
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
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
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
> 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 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
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
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
k: compilers/tge/TGE
languages/tcl/config/makefiles languages/tcl/lib languages/tcl/src
languages/tcl/t runtime/parrot/library/PGE src
Author: paultcochrane
Date: Fri Jan 19 03:06:07 2007
New Revision: 16706
Modified:
trunk/compilers/tge/TGE/Compiler.pir
trunk/languages/tcl/config/makefi
10 matches
Mail list logo
