discuss code archived in pre-github branches

[slayoo]

There are three development (i.e. work-in-progress?) branches preserved from pre-github times (see https://github.com/blitzpp/blitz/branches):

• stencil-et
• compat-64bit
• vectorization

Would be great to leverage the code developed there!

[citibeth]

Would you like to submit a pull request to the Git repo?

BTW... I consider Blitz++ to be in strictly maintenance mode. On my off-hours, I'm working on a replacement that will work more seamlessly with C++11.

-- Elizabeth

On Wed, Mar 28, 2018 at 3:46 PM, Sylwester Arabas notifications@github.com wrote:

There are three development (i.e. work-in-progress?) branches preserved from pre-github times (see https://github.com/blitzpp/blitz/branches):

• stencil-et
• compat-64bit
• vectorization

Would be great to leverage the code developed there!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/blitzpp/blitz/issues/26, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1cd0afKfw1bG7NAS-V8h79TeEJ7dEeks5ti-h6gaJpZM4S_P6f .

[lutorm]

As noted on those branches, the relevant code has already been merged.

Cheers,

/Patrik

On Wed, Mar 28, 2018 at 9:46 AM, Sylwester Arabas notifications@github.com wrote:

There are three development (i.e. work-in-progress?) branches preserved from pre-github times (see https://github.com/blitzpp/blitz/branches):

• stencil-et
• compat-64bit
• vectorization

Would be great to leverage the code developed there!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/blitzpp/blitz/issues/26, or mute the thread https://github.com/notifications/unsubscribe-auth/AFK8GMr8KC4q1f5S1DilvTqxcsdnWNyHks5ti-h6gaJpZM4S_P6f .

[slayoo]

Great! Thank you Patrik! Elisabeth, I'm looking forward to hearing more news! P.S. I'm working right now on Travis and Appveyor continuous integration scripts for this repo, pull request soon. Sylwester

[slayoo]

Well, in fact reopening as perhaps these branches could be deleted then?

[lutorm]

I think the correct action in hg is to "close" the branches, which I did. I don't think you can delete them in hg.

If they're still showing up in git, then yeah, they can be deleted.

On Wed, Mar 28, 2018 at 10:07 AM, Sylwester Arabas <notifications@github.com

wrote:

Well, in fact reopening as perhaps these branches could be deleted then?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/blitzpp/blitz/issues/26#issuecomment-377018752, or mute the thread https://github.com/notifications/unsubscribe-auth/AFK8GAljLPk-JujN9iZE0MK7FbpedyYbks5ti-15gaJpZM4S_P6f .

[slayoo]

On github they still show up as candidates for pull requests, in the branches tab there are the red trash bin icons to delete/deactivate them:

[slayoo]

Here is the Travis-CS pull request:https://github.com/blitzpp/blitz/pull/27

[slayoo]