Not sure about the pull request part, but here's a place to start:
https://github.com/apache/derby
bryan
On Mon, Dec 17, 2018 at 6:21 PM Alex O'Ree wrote:
>
> Which merge tool is good in your opinion? I've used the tortoise products
> with good results
>
> Also, if mirroring to github is
Which merge tool is good in your opinion? I've used the tortoise products
with good results
Also, if mirroring to github is enabled for this project and you can accept
PRs from it, then this is a moot conversation.
On Mon, Dec 17, 2018 at 8:34 PM Rick Hillegas
wrote:
> I appreciate your
I appreciate your willingness to contribute. Nevertheless, I think that
* git is a poor fit for Derby's culture of incremental development and
is, instead, better suited to large projects where teams work in
isolation from one another on large contributions
* git has the worst merge tool I
I thought we already had a git mirror for the svn repo for Derby.
I thought Knut Anders already used it quite successfully for his contributions.
Perhaps he will respond to this email with more details?
If not, I can probably search the archives.
bryan
On Mon, Dec 17, 2018 at 4:20 PM Alex
I wasn't at first either. It seems unnecessary at a glance. It does greatly
simplify accepting contributions from users without commit rights. For
outside committers, they can commit as much as they need to without
affecting the baseline. Which makes things much easier for larger tasks.
Pull
On 12/16/18 4:16 PM, Alex O'Ree wrote:
Has anyone suggested switching to git? ASF makes the change pretty
painless
I'm not a git enthusiast.
