[Pdl-devel] Code review: branch travis-ci-more [Travis-CI changes and build improvements]

View code: - Sourceforge: - GitHub: CI: - Build #25 Summary: 1. @mohawk2 has worked on incorporating the code for the pre-req report f

Re: [Pdl-devel] Git configuration policy question: forbid merge commits?

> A better solution would be to clarify a good git workflow > standard for PDL, document things, discuss what makes > sense on the pdl-devel list, and then implement appropriately. I agree! Hence my email. So, what are your thoughts on merge commits? --

Re: [Pdl-devel] Crufty git branches

Great, done that. Re making a branch, remember we can always go back and do that should the necessity arise, even if the “master” pointer has moved past it. From: Chris Marshall Sent: Saturday, February 28, 2015 8:50 PM To: Ed ; pdl-devel Subject: Re: [Pdl-devel] Crufty git branches I'm fine w

Re: [Pdl-devel] Git configuration policy question: forbid merge commits?

All- A lot of the perceived problems come from one developer assuming a work flow for a branch not originated by them. For example LLDF was a one-off branch that was intended to provide visibility and opportunity for developers to see and/or help with fixing the 64bit index issues. In hindsight

Re: [Pdl-devel] Git configuration policy question: forbid merge commits?

Could we please avoid re-configuration of the git until things are stable after 2.008 is released and we have some sort of plan for a PDL git workflow standard? --Chris On 2/28/2015 15:36, Ed wrote: Dear PDL devs, I would like to get consensus on this: should merge commits be forbidden? In my r

Re: [Pdl-devel] Sourceforge Git config - force-push allowed

Could we please avoid re-configuration of the git until things are stable after 2.008 is released and we have some sort of plan for a PDL git workflow standard? --Chris On 2/28/2015 15:19, Ed wrote: Dear PDL devs, I have set the Git configuration to now allow force-pushes. This is essential fo

Re: [Pdl-devel] Crufty git branches

I'm fine with deleting the following branches from PDL code: cpan_2.006_release cpan_2.007_04 cpan_2.007_release release_2.4.10 We can always generate a real branch at the release tag if maintenance is needed for a release separate from the on-going development. --Chris On 2/28/2015 14

[Pdl-devel] Git configuration policy question: forbid merge commits?

Dear PDL devs, I would like to get consensus on this: should merge commits be forbidden? In my recent experience with core-cleanup and LLDF, their use by some devs has led to serious confusion, especially when the merge commit has led to changes being silently dropped despite the commits being

[Pdl-devel] Sourceforge Git config - force-push allowed

Dear PDL devs, I have set the Git configuration to now allow force-pushes. This is essential for topic branches. It is now physically possible on master, but it is bad practice to use it on that, so please don’t. Best regards, Ed--

[Pdl-devel] Crufty git branches

Hi PDL devs, Looking at this: https://github.com/PDLPorters/pdl/branches Shows that these branches, having “0” on the right side of the little graphs, don’t ADD any commits: * cpan_2.007_release * release_2.4.10 They appear to be in fact doing what a tag does, which is mark a point in time, an