Yet another (albeit a bit roundabout) approach would be to use the GitHub
mirror here: https://github.com/apache/flex
You can fork a new GitHub project for each patch you are planning to
create. Each one forks off of the main flex github. You can create
patches individually and attach them to co
On 8/8/12 5:54 AM, "Justin Mclean" wrote:
> Hi,
>
> Interesting issue and probably not one correct answer.
>
> I'd go with generating patches against the latest SVN head as they can be
> easily applied.
>
> I'd try and keep in sync with the trunk (ie svn update) but no need to revert
> to
Hi,
Interesting issue and probably not one correct answer.
I'd go with generating patches against the latest SVN head as they can be
easily applied.
I'd try and keep in sync with the trunk (ie svn update) but no need to revert
to it as that would mean more work for you.
Thanks,
Justin
Hi,
Any help you can give me with the following is very much appreciated:
I'm currently helping Om with the InstallApacheFlex app. I'm have a
basic knowledge of how patches are created and applied in SVN. I have
even submitted several patches already, which Om was kind enough to
commit to the rep
