[COMMIT] imcc moves out of languages

2003-10-22 Thread Melvin Smith
IMCC has graduated from the parrot/languages/imcc directory to parrot/imcc.
Please update your trees.
We may still want to move the main up to the parrot directory and
possibly do an include/imcc directory, but I'm not sure.
Test builds on my machine, so I think everything is back to intact for now.

-Melvin




Re: [COMMIT] imcc moves out of languages

2003-10-22 Thread Robert Spier

So much for preserving repository history.

(Dan!  Where's the list of things to move?)

-R

At Wed, 22 Oct 2003 22:29:49 -0400,
Melvin Smith wrote:
> 
> IMCC has graduated from the parrot/languages/imcc directory to parrot/imcc.
> Please update your trees.
> 
> We may still want to move the main up to the parrot directory and
> possibly do an include/imcc directory, but I'm not sure.
> 
> Test builds on my machine, so I think everything is back to intact for now.
> 
> -Melvin
> 


Re: [COMMIT] imcc moves out of languages

2003-10-22 Thread Melvin Smith
Well, if you want to roll it back I don't mind. I don't
think there were any other commits during my
little hack and slash.
We probably shouldn't worry too much while
still in 0.0.x stage until we at least have a beta
release (or whatever 0.1 is going to be).
Then revision history becomes much more important.

-Melvin

At 09:45 PM 10/22/2003 -0700, Robert Spier wrote:

So much for preserving repository history.

(Dan!  Where's the list of things to move?)

-R

At Wed, 22 Oct 2003 22:29:49 -0400,
Melvin Smith wrote:
>
> IMCC has graduated from the parrot/languages/imcc directory to parrot/imcc.
> Please update your trees.
>
> We may still want to move the main up to the parrot directory and
> possibly do an include/imcc directory, but I'm not sure.
>
> Test builds on my machine, so I think everything is back to intact for now.
>
> -Melvin
>




Re: [COMMIT] imcc moves out of languages

2003-10-22 Thread Leopold Toetsch
Robert Spier <[EMAIL PROTECTED]> wrote:

[ quoting reordered ]

> Melvin Smith wrote:
>>
>> IMCC has graduated from the parrot/languages/imcc directory to parrot/imcc.

Arghh[1]

> So much for preserving repository history.

Yep. Is the history gone, or are you able to do something for it?

> -R

[1] There was a lot of discussion on the list, how and why we will move
files around. Melvin, please (re)read p6i or perl.perl6.internals


Re: [COMMIT] imcc moves out of languages

2003-10-23 Thread Michael Scott
Shouldn't imcc/docs (eventually) be docs/imcc, and imcc/t be t/imcc?

Mike

On Thursday, Oct 23, 2003, at 04:29 Europe/Berlin, Melvin Smith wrote:

IMCC has graduated from the parrot/languages/imcc directory to 
parrot/imcc.
Please update your trees.

We may still want to move the main up to the parrot directory and
possibly do an include/imcc directory, but I'm not sure.
Test builds on my machine, so I think everything is back to intact for 
now.

-Melvin





Re: [COMMIT] imcc moves out of languages

2003-10-23 Thread Dan Sugalski
On Thu, 23 Oct 2003, Michael Scott wrote:

> Shouldn't imcc/docs (eventually) be docs/imcc, and imcc/t be t/imcc?

Yeah, but lets deal with the initial aftermat first...

> On Thursday, Oct 23, 2003, at 04:29 Europe/Berlin, Melvin Smith wrote:
>
> > IMCC has graduated from the parrot/languages/imcc directory to
> > parrot/imcc.
> > Please update your trees.
> >
> > We may still want to move the main up to the parrot directory and
> > possibly do an include/imcc directory, but I'm not sure.
> >
> > Test builds on my machine, so I think everything is back to intact for
> > now.
> >
> > -Melvin
> >
> >
>

Dan

--"it's like this"---
Dan Sugalski  even samurai
[EMAIL PROTECTED] have teddy bears and even
  teddy bears get drunk



Re: [COMMIT] imcc moves out of languages

2003-10-23 Thread Michael Scott
Almost forgot: imcc/examples to be (eventually) examples/imcc.

Mike



Re: [COMMIT] imcc moves out of languages

2003-10-23 Thread Melvin Smith
At 08:41 AM 10/23/2003 +0200, Leopold Toetsch wrote:
Robert Spier <[EMAIL PROTECTED]> wrote:

[ quoting reordered ]

> Melvin Smith wrote:
>>
>> IMCC has graduated from the parrot/languages/imcc directory to 
parrot/imcc.

Arghh[1]
Ok guys, let us not make mountains out of molehills.

> So much for preserving repository history.

Yep. Is the history gone, or are you able to do something for it?
Does it really matter at 0.0.11 ??

[1] There was a lot of discussion on the list, how and why we will move
files around. Melvin, please (re)read p6i or perl.perl6.internals
Leo, there is always a lot of discussion, and my apologies for not
reading every last line, I do my best between jobs.
We have a snapshot from last night before my change. If it means
that much, hopefully Robert can work some magic, or move it back
where it was and I'll happily clean up the mess.
-Melvin




Re: [COMMIT] imcc moves out of languages

2003-10-23 Thread Robert Spier
> > So much for preserving repository history.
> Yep. Is the history gone, or are you able to do something for it?

I've reattached the history to the files.  All should be well.

Depending on when you last updated, you _may_ see weird warnings on
your next update -- they should be harmless.

-R



Re: [COMMIT] imcc moves out of languages

2003-10-23 Thread Leopold Toetsch
Robert Spier <[EMAIL PROTECTED]> wrote:
>> > So much for preserving repository history.
>> Yep. Is the history gone, or are you able to do something for it?

> I've reattached the history to the files.  All should be well.

Thanks again for keeping the machinery running,

leo


Re: [COMMIT] imcc moves out of languages

2003-10-23 Thread mrjoltcola
Thanks Robert for the fixup.
Nothing like throwing a grenade to get people scrambling.

-Melvin


-Original Message-
From: Robert Spier <[EMAIL PROTECTED]>
Sent: Oct 23, 2003 1:33 PM
To: [EMAIL PROTECTED]
Subject: Re: [COMMIT] imcc moves out of languages

> > So much for preserving repository history.
> Yep. Is the history gone, or are you able to do something for it?

I've reattached the history to the files.  All should be well.

Depending on when you last updated, you _may_ see weird warnings on
your next update -- they should be harmless.

-R