[BCEL] Move to Git?

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

[BCEL] Move to Git?

Andrey Loskutov
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

garydgregory
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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
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
Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

jochen-2
On Tue, Jun 7, 2016 at 10:43 AM, Gary Gregory <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

garydgregory
On Tue, Jun 7, 2016 at 1:46 AM, Jochen Wiedmann <[hidden email]>
wrote:

> On Tue, Jun 7, 2016 at 10:43 AM, Gary Gregory <[hidden email]>
> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
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
Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

James Carman
In reply to this post by jochen-2
This was proposed long ago.

On Tue, Jun 7, 2016 at 4:46 AM Jochen Wiedmann <[hidden email]>
wrote:

> On Tue, Jun 7, 2016 at 10:43 AM, Gary Gregory <[hidden email]>
> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

Benedikt Ritter-4
James Carman <[hidden email]> 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 <[hidden email]>
> wrote:
>
> > On Tue, Jun 7, 2016 at 10:43 AM, Gary Gregory <[hidden email]>
> > 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: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

Benedikt Ritter-4
In reply to this post by Andrey Loskutov
Hello Andrey,

right now I think it would be better to focus on the next release and do
the migration afterwards.

Benedikt

Andrey Loskutov <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

Andrey Loskutov
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 <[hidden email]> 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: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >

--
Kind regards,
google.com/+AndreyLoskutov

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

Benedikt Ritter-4
Hello Andrey,

Andrey Loskutov <[hidden email]> 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 <[hidden email]> 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: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > >
>
> --
> Kind regards,
> google.com/+AndreyLoskutov
>
Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Move to Git?

Andrey Loskutov
On Tuesday 07 June 2016 15:25 Benedikt Ritter wrote:

> Hello Andrey,
>
> Andrey Loskutov <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]