>> Who are those people? Maybe they should comment on this? I am one of those people. At this point I have minimal (if any) understanding of the actual patch insertion process, but given I don't have write privileges that is okay. I also have minimal/no understanding of how to apply patches that are not "committed" to something I am building. (I know I need to read the manual.) I have no allegiance to SVN other than I know I will face it again in the future.
What are the advantages (and disadvantages) to what Dominik is proposing? I have never dealt with BitBucket or any of the other items mentioned. To be honest, when I first read the description, my eyes started rolling as my brain said what is all this? I thought it was a duplication of effort, but Stefan seems to think it may have merit, so what is the merit? Dominik, please understand that no insult is intended in any of my comments above. They all stem from my lack of knowledge of the tools in this space and mostly likely show my ignorance. ---------------------------------------------------------------------- Roy Chastain -----Original Message----- From: Dominik Psenner [mailto:dpsen...@gmail.com] Sent: Saturday, August 13, 2011 03:56 To: log4net-dev@logging.apache.org Subject: Re: Moving forward with updates, builds and versions On 08/13/2011 06:30 AM, Stefan Bodewig wrote: > We do have a read-only git version at git://git.apache.org/log4net.git > <http://git.apache.org/log4net.git/> mirrored at github as well > <https://github.com/apache/log4net> Didn't know that. :-) Since that repository is read-only, it is not exactly a great help for whoever wants to hack on log4net now. > > Given that svn is new to some of the people who raised their hand to > help I'm a bit reluctant to add yet another tool new to them to the > mix (and throw in something like git-svn or hg-svn on top of that). > Combine that with the change in philosophy a distributed VCS brings. If they're new to svn, it would actually be no great effort to learn another tool. > > I agree this would work and would be willing to give it a try with > people who want to work that way. But this really depends on the > people who will actually do the commit to svn (which I currently can't > do myself either). Who are those people? Maybe they should comment on this?
