copy files over and see if you can merge and commit/push
What would mean deleting the current tree and copy the new one over and not
only copy over the existing tree as it would be a problem if parts of the
tree have been renamed or moved, right ?
The main difference is it easier to check out part of a repo in SVN so
with Git or Github we may want a repo/committer rather than a single repo.
It's not really the github way and would mean that a github contributor
would be able to send pull requests touching files in a project is not
initially contributing and has not the agreement of the committer, so to
make it work, it would imply more checks for the committer reviewing the
pull request before to integrate it but it should be possible I think.
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Tuesday, April 09, 2013 8:45 AM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] How do we want to handle Whiteboard?
Hi,
I would like to remind you the technical problem to do it
If the whiteboard is in SVN, Git or Github we have the same issue - the
white board area doesn't have to mirror the current SDK structure. Answer
is basically patch files in JIRA or branch existing SDK copy files over and
see if you can merge and commit/push.
The main difference is it easier to check out part of a repo in SVN so with
Git or Github we may want a repo/committer rather than a single repo.
Thanks,
Justin
