On Sat, Sep 3, 2016 at 9:45 PM Dammina Sahabandu <[email protected]> wrote:
> Hi Ryan, > > Thank you very much for the information and the guide. The last version > merged into Bloodhound was Trac 1.0.1 in 2013. So I guess it will be easier > for us to first move into Trac 1.0.12 and then to Trac 1.2. I have started > applying the generated custom set of patches to the new sub-repo (Trac > 1.0.12). After I have completed the process I will notify you and if time > permits it would be really great if you can review the change set. > Feel free to share work in progress as well. Since you asked about a branch in the repository, do you plan to work from SVN? You should use what you are comfortable with, but for this use-case, I think the patch management will be easier in Git, assuming you are comfortable with the tool. I like SVN, but in cases like this I find the patch management to be easier in DVCS that supports rebasing. Here is the Git mirror, in case you weren't aware of the location. https://github.com/apache/bloodhound/tree/trunk - Ryan
