Re: [ALL] Git repository for a sandbox component?

GitHub mirrors both the svn and git repos for ASF projects, so you get the advantages either way. Merging pull requests from GitHub is easier via git, but they do provide .patch files as well which work just as well in svn. On 5 November 2016 at 13:54, Eric Barnhill

Re: [ALL] Git repository for a sandbox component?

On Sat, 5 Nov 2016 19:54:02 +0100, Eric Barnhill wrote: Speaking for myself either is fine. I find svn commands easier to deal with than git, but github is easy to use as a site. I find the above a little contradictory but since you are going to manage this, it's up to you. ;-) Gilles

Re: [ALL] Git repository for a sandbox component?

Speaking for myself either is fine. I find svn commands easier to deal with than git, but github is easy to use as a site. Eric On Sat, Nov 5, 2016 at 4:43 PM, Gilles wrote: > On Sat, 5 Nov 2016 09:53:01 -0500, Matt Sicker wrote: > >> Is this a vote of some sort

Re: [ALL] Git repository for a sandbox component?

On Sat, 5 Nov 2016 09:53:01 -0500, Matt Sicker wrote: Is this a vote of some sort to convert from svn? Not really (at least if your question is whether I ask to convert the whole sandbox, or all sandbox components). I thought that a sandbox component had to use the same repository as all

Re: [ALL] Git repository for a sandbox component? (Was: commons-filter sandbox is operational)

Is this a vote of some sort to convert from svn? So far we've all been pretty on board with migrating Commons projects to git. On 4 November 2016 at 16:27, Gilles wrote: > Hello. > > I noticed that the "Text" component uses "git". > It would be simpler to also use

[ALL] Git repository for a sandbox component? (Was: commons-filter sandbox is operational)

Hello. I noticed that the "Text" component uses "git". It would be simpler to also use git for the "filter" component. Regards, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands,