You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Andrey Loskutov <lo...@gmx.de> on 2016/06/07 08:40:33 UTC
[BCEL] Move to Git?
Hi all,
I'm not a BCEL developer, just a user, but may I trigger a discussion to move BCEL development from SVN to Git?
I see there is already a Github mirror, so may be it is not that complicated?
The main resson is to simplify contributions. I've made few smaller commits on BCEL trunk via Git clone (see [1]) but because I do not have commit rights in SVN I'm forced to create patches. This is very cumbersome. Given that there aren't much contributors, we schould lower the barrier for new people, and having a possibility to create and manage Git pull requests is definitely a time saver, not mentioning here all other benefits Git offers over SVN.
Comments?
[1] https://github.com/iloveeclipse/commons-bcel/commits/trunk
--
Kind regards,
Andrey Loskutov
http://google.com/+AndreyLoskutov
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [BCEL] Move to Git?
Posted by Benedikt Ritter <br...@apache.org>.
James Carman <ja...@carmanconsulting.com> schrieb am Di., 7. Juni 2016 um
12:51 Uhr:
> This was proposed long ago.
>
exactly. So it's probably a good idea to rethink our decision now more
people have the necessary experience with git.
>
> On Tue, Jun 7, 2016 at 4:46 AM Jochen Wiedmann <jo...@gmail.com>
> wrote:
>
> > On Tue, Jun 7, 2016 at 10:43 AM, Gary Gregory <ga...@gmail.com>
> > wrote:
> >
> > > We have a bunch of components that just got in the queue to migrate
> from
> > > Svn to Git. BCEL would just be another one...
> >
> > Maybe we could take the discussion for all components now, and would
> > just do the actual move componentwise?
> >
> > - Would spare us a lot of [VOTE][LAZY] mails.
> > - At least I don't see anyone opposing.
> >
> > Jochen
> >
> >
> >
> > --
> > The next time you hear: "Don't reinvent the wheel!"
> >
> >
> >
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
Re: [BCEL] Move to Git?
Posted by James Carman <ja...@carmanconsulting.com>.
This was proposed long ago.
On Tue, Jun 7, 2016 at 4:46 AM Jochen Wiedmann <jo...@gmail.com>
wrote:
> On Tue, Jun 7, 2016 at 10:43 AM, Gary Gregory <ga...@gmail.com>
> wrote:
>
> > We have a bunch of components that just got in the queue to migrate from
> > Svn to Git. BCEL would just be another one...
>
> Maybe we could take the discussion for all components now, and would
> just do the actual move componentwise?
>
> - Would spare us a lot of [VOTE][LAZY] mails.
> - At least I don't see anyone opposing.
>
> Jochen
>
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [BCEL] Move to Git?
Posted by Gary Gregory <ga...@gmail.com>.
On Tue, Jun 7, 2016 at 1:46 AM, Jochen Wiedmann <jo...@gmail.com>
wrote:
> On Tue, Jun 7, 2016 at 10:43 AM, Gary Gregory <ga...@gmail.com>
> wrote:
>
> > We have a bunch of components that just got in the queue to migrate from
> > Svn to Git. BCEL would just be another one...
>
> Maybe we could take the discussion for all components now, and would
> just do the actual move componentwise?
>
> - Would spare us a lot of [VOTE][LAZY] mails.
> - At least I don't see anyone opposing.
>
I'd rather have it all in one place myself but it's a lot of busy work I do
not need ATM.
Gary
>
> Jochen
>
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [BCEL] Move to Git?
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Tue, Jun 7, 2016 at 10:43 AM, Gary Gregory <ga...@gmail.com> wrote:
> We have a bunch of components that just got in the queue to migrate from
> Svn to Git. BCEL would just be another one...
Maybe we could take the discussion for all components now, and would
just do the actual move componentwise?
- Would spare us a lot of [VOTE][LAZY] mails.
- At least I don't see anyone opposing.
Jochen
--
The next time you hear: "Don't reinvent the wheel!"
http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [BCEL] Move to Git?
Posted by Gary Gregory <ga...@gmail.com>.
We have a bunch of components that just got in the queue to migrate from
Svn to Git. BCEL would just be another one...
Gary
On Tue, Jun 7, 2016 at 1:40 AM, Andrey Loskutov <lo...@gmx.de> wrote:
> Hi all,
>
> I'm not a BCEL developer, just a user, but may I trigger a discussion to
> move BCEL development from SVN to Git?
> I see there is already a Github mirror, so may be it is not that
> complicated?
>
> The main resson is to simplify contributions. I've made few smaller
> commits on BCEL trunk via Git clone (see [1]) but because I do not have
> commit rights in SVN I'm forced to create patches. This is very cumbersome.
> Given that there aren't much contributors, we schould lower the barrier for
> new people, and having a possibility to create and manage Git pull requests
> is definitely a time saver, not mentioning here all other benefits Git
> offers over SVN.
>
> Comments?
>
> [1] https://github.com/iloveeclipse/commons-bcel/commits/trunk
> --
> Kind regards,
> Andrey Loskutov
>
> http://google.com/+AndreyLoskutov
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [BCEL] Move to Git?
Posted by Andrey Loskutov <lo...@gmx.de>.
On Tuesday 07 June 2016 15:25 Benedikt Ritter wrote:
> Hello Andrey,
>
> Andrey Loskutov <lo...@gmx.de> schrieb am Di., 7. Juni 2016 um 17:19 Uhr:
>
> > On Tuesday 07 June 2016 15:10 Benedikt Ritter wrote:
> > > Hello Andrey,
> > >
> > > right now I think it would be better to focus on the next release and do
> > > the migration afterwards.
> >
> > My point was: I'm willing to help as far as I can (we need a solid BCEL
> > release for FindBugs), but I'm not willing to use SVN. It is stone age.
> > It just incredible waste of my/others time, and none of us has lot of free
> > time.
> > The SVN history, branching, *everything* feels so slow/not usable after
> > working with Mercurial or Git, that it just wondered if it is time to
> > switch.
> >
> > But sure, if it is not an easy task, please focus resources on release.
> >
>
> You can contribute via GitHub PRs. We will apply those fixes to SVN which
> will get mirrored to GitHub.
OK, this sound good.
--
Kind regards,
google.com/+AndreyLoskutov
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [BCEL] Move to Git?
Posted by Benedikt Ritter <br...@apache.org>.
Hello Andrey,
Andrey Loskutov <lo...@gmx.de> schrieb am Di., 7. Juni 2016 um 17:19 Uhr:
> On Tuesday 07 June 2016 15:10 Benedikt Ritter wrote:
> > Hello Andrey,
> >
> > right now I think it would be better to focus on the next release and do
> > the migration afterwards.
>
> My point was: I'm willing to help as far as I can (we need a solid BCEL
> release for FindBugs), but I'm not willing to use SVN. It is stone age.
> It just incredible waste of my/others time, and none of us has lot of free
> time.
> The SVN history, branching, *everything* feels so slow/not usable after
> working with Mercurial or Git, that it just wondered if it is time to
> switch.
>
> But sure, if it is not an easy task, please focus resources on release.
>
You can contribute via GitHub PRs. We will apply those fixes to SVN which
will get mirrored to GitHub.
>
> > Benedikt
> >
> > Andrey Loskutov <lo...@gmx.de> schrieb am Di., 7. Juni 2016 um 10:40
> Uhr:
> >
> > > Hi all,
> > >
> > > I'm not a BCEL developer, just a user, but may I trigger a discussion
> to
> > > move BCEL development from SVN to Git?
> > > I see there is already a Github mirror, so may be it is not that
> > > complicated?
> > >
> > > The main resson is to simplify contributions. I've made few smaller
> > > commits on BCEL trunk via Git clone (see [1]) but because I do not have
> > > commit rights in SVN I'm forced to create patches. This is very
> cumbersome.
> > > Given that there aren't much contributors, we schould lower the
> barrier for
> > > new people, and having a possibility to create and manage Git pull
> requests
> > > is definitely a time saver, not mentioning here all other benefits Git
> > > offers over SVN.
> > >
> > > Comments?
> > >
> > > [1] https://github.com/iloveeclipse/commons-bcel/commits/trunk
> > > --
> > > Kind regards,
> > > Andrey Loskutov
> > >
> > > http://google.com/+AndreyLoskutov
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
>
> --
> Kind regards,
> google.com/+AndreyLoskutov
>
Re: [BCEL] Move to Git?
Posted by Andrey Loskutov <lo...@gmx.de>.
On Tuesday 07 June 2016 15:10 Benedikt Ritter wrote:
> Hello Andrey,
>
> right now I think it would be better to focus on the next release and do
> the migration afterwards.
My point was: I'm willing to help as far as I can (we need a solid BCEL release for FindBugs), but I'm not willing to use SVN. It is stone age.
It just incredible waste of my/others time, and none of us has lot of free time.
The SVN history, branching, *everything* feels so slow/not usable after working with Mercurial or Git, that it just wondered if it is time to switch.
But sure, if it is not an easy task, please focus resources on release.
> Benedikt
>
> Andrey Loskutov <lo...@gmx.de> schrieb am Di., 7. Juni 2016 um 10:40 Uhr:
>
> > Hi all,
> >
> > I'm not a BCEL developer, just a user, but may I trigger a discussion to
> > move BCEL development from SVN to Git?
> > I see there is already a Github mirror, so may be it is not that
> > complicated?
> >
> > The main resson is to simplify contributions. I've made few smaller
> > commits on BCEL trunk via Git clone (see [1]) but because I do not have
> > commit rights in SVN I'm forced to create patches. This is very cumbersome.
> > Given that there aren't much contributors, we schould lower the barrier for
> > new people, and having a possibility to create and manage Git pull requests
> > is definitely a time saver, not mentioning here all other benefits Git
> > offers over SVN.
> >
> > Comments?
> >
> > [1] https://github.com/iloveeclipse/commons-bcel/commits/trunk
> > --
> > Kind regards,
> > Andrey Loskutov
> >
> > http://google.com/+AndreyLoskutov
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
--
Kind regards,
google.com/+AndreyLoskutov
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [BCEL] Move to Git?
Posted by Benedikt Ritter <br...@apache.org>.
Hello Andrey,
right now I think it would be better to focus on the next release and do
the migration afterwards.
Benedikt
Andrey Loskutov <lo...@gmx.de> schrieb am Di., 7. Juni 2016 um 10:40 Uhr:
> Hi all,
>
> I'm not a BCEL developer, just a user, but may I trigger a discussion to
> move BCEL development from SVN to Git?
> I see there is already a Github mirror, so may be it is not that
> complicated?
>
> The main resson is to simplify contributions. I've made few smaller
> commits on BCEL trunk via Git clone (see [1]) but because I do not have
> commit rights in SVN I'm forced to create patches. This is very cumbersome.
> Given that there aren't much contributors, we schould lower the barrier for
> new people, and having a possibility to create and manage Git pull requests
> is definitely a time saver, not mentioning here all other benefits Git
> offers over SVN.
>
> Comments?
>
> [1] https://github.com/iloveeclipse/commons-bcel/commits/trunk
> --
> Kind regards,
> Andrey Loskutov
>
> http://google.com/+AndreyLoskutov
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>