On Feb 17, 2008 9:01 PM, Jim Ursetto <[EMAIL PROTECTED]> wrote:
> Yes. The toplevel directory is for release 2 only, and will
> probably be renamed later to release/2, but has not yet
> been to retain backwards compatibility.
>
Moving all the stuff into a "release/2" directory should
probably wor
Yes. The toplevel directory is for release 2 only, and will
probably be renamed later to release/2, but has not yet
been to retain backwards compatibility.
On 2/17/08, Shawn <[EMAIL PROTECTED]> wrote:
> Should all new eggs be created in chicken-eggs/release/3 instead of
> the toplevel chicken-egg
On Feb 15, 2008, at 8:39 PM, Graham Fawcett wrote:
Hi folks,
I just started a new egg in the svn repo. It's nothing worth
looking at yet, I just want to make sure I didn't do something
stupid that would break anything. Here's what I did:
cd release/3/
svn mkdir locality
Should all new
>
> This won't release an egg, or mess with any of the server-side tasks, will
> it?
>
> No. Only if tags/xxx exists.
>
(or if you omit the trunk dir and a .meta file exists)
cheers,
felix
___
Chicken-users mailing list
Chicken-users@nongnu.org
http
On Feb 15, 2008, at 8:39 PM, Graham Fawcett wrote:
Hi folks,
I just started a new egg in the svn repo. It's nothing worth
looking at yet, I just want to make sure I didn't do something
stupid that would break anything. Here's what I did:
cd release/3/
svn mkdir locality
svn mkdir localit
Hi folks,
I just started a new egg in the svn repo. It's nothing worth looking at yet,
I just want to make sure I didn't do something stupid that would break
anything. Here's what I did:
cd release/3/
svn mkdir locality
svn mkdir locality/trunk
cp locality/trunk
svn commit locality
This won't r
