I agree,
When I used svn, I created a folder 'whiteboard/mschmalle' and only
checked out mine.
The way it's setup is not usable for sure. I'm just ditching the
premise of a whiteboard as it stands.
Mike
Quoting Frédéric THOMAS <webdoubl...@hotmail.com>:
The flex-whiteboard is too big, it takes ages to download, it's not
really handy that every whiteboards are inside, some of us putted
the entire sdk, so it takes to much space and if someone want to
checkout its own one, he has to checkout every whiteboards, it's not
good to me, how did they do on the other apache projects ? I don't
know if it's possible but I would rather prefer everyone has its own
git repo.
-Fred
-----Message d'origine----- From: Frédéric THOMAS
Sent: Sunday, March 17, 2013 1:53 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Hi,
I just committed the .gitignore into the flex-sdk repo, I'm checking how are
flex-utilities and flex-whiteboard (at least mine) today, while I'll
probably put the same .gitignore in the flex-utilities repo, I advice you
guys to do the same with your personal repo.
Thinking about the asjs project, you can as well do the same, you'll have to
add some more exclusions.
@Justin, I really don't know what to write on the wiki about that, it's like
if we wanted to write something about svnignore, there is not so much to
say, once it is in the repo, it does what is has to do, that's it.
If you think about something in particular I should write about it, tell me
pls because I'm like in front of a white page at the moment.
Thanks,
-Fred
-----Message d'origine----- From: Justin Mclean
Sent: Sunday, March 17, 2013 1:28 AM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Hi,
Btw, to all of you, I'm thinking about committing this file to svn,
like that when we'll clone the git repo, we'll already have it,
avoiding bad commits, what do you think ?
Add it to the "official" wiki page on git usage for Apache Flex - which
still needs some work.
Justin
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
