As I am digging further into this though, I am coming up with a lot of
questions. I am guessing, based on the fact that I am seeing whiteboards,
etc. that committers don't really have their own forks in our current
apache model, but rather everyone is using their own clone of the same
fork. Am I right? Is there a particular reason we went this way?
You are right and they just copied the whiteboards into one git repo.
What to do with Whiteboard?
1. Use the sparse checkout option as described here (
http://markmail.org/message/dg7hplezkzwiroes)
2. Create a branch per user in the whiteboard
3. Move to github for whiteboards
4. Let whiteboards remain in SVN
None of the above solutions suits me, my requirement would be (as it should
from the Git model), not only to have one repo per person but one per
project (people might have several projects in their whiteboard) which is
not feasible, not even one per person as someone 'guessed', the only way I
can see to reach it's requirement, is to stay in Svn and do and git-svn over
the project you want to have a git equivalent if you really want it as
git-svn is very slow to initialize.
Thanks,
-Fred
-----Message d'origine-----
From: Michael A. Labriola
Sent: Sunday, March 24, 2013 6:48 AM
To: dev@flex.apache.org
Subject: RE: [Git/Wiki] please review the proposed workflow and comment
I'd rather see links to the best example elsewhere on the net or short
stories as to what rebase does, or why cutting a branch saved your ass,
along with steps to do it and what those steps are doing. Git seems
>powerful enough that if you don't know what you are doing you can make a
lot of work for yourself or others.
Alex,
Agreed. I think we will get there.
Fred,
As I am digging further into this though, I am coming up with a lot of
questions. I am guessing, based on the fact that I am seeing whiteboards,
etc. that committers don't really have their own forks in our current apache
model, but rather everyone is using their own clone of the same fork. Am I
right? Is there a particular reason we went this way?
I am just trying to understand so I can do my best to guide us within the
model that has been created. There could be many viable reasons for this but
to me, right now, it's a little strange for a git project, so I am just
trying to grok it all. This would change some of the advice I gave Alex, for
example.
Mike
