New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dangerous branch names in the security repository #12791
Comments
From @nwc10Right now the branch names for blead and maint-* are the same in the If we don't change this, that won't be the last time :-( In another message, I suggested: 1) change the branch names to sec-blead, sec-maint-5.16 etc in the security I think that this will solve the problem, without making life too hard for Should we do this? Nicholas Clark |
From @nwc10On Mon Feb 18 07:07:35 2013, nicholas wrote: Forgot the PS - I think that this ticket can go public once Nicholas Clark |
@nwc10 - Status changed from 'new' to 'open' |
From @demerphqOn Mon Feb 18 07:07:35 2013, nicholas wrote:
Well if people set up their remotes properly, unlike me, then it is less I think as part of this ticket we should also figure out how to ensure Yves |
Migrated from rt.perl.org#116839 (status was 'open')
Searchable as RT116839$
The text was updated successfully, but these errors were encountered: