develooper Front page | perl.perl5.porters | Postings from January 2020

mononomial versus binomial branch names.

Thread Next
From:
demerphq
Date:
January 31, 2020 15:00
Subject:
mononomial versus binomial branch names.
Message ID:
CANgJU+VgMNwPw6B446z_T1T0HANcLrw8XedW9_joq+rmj3iZRQ@mail.gmail.com
I noticed that we have a few mononomial branch names. For instance Todd
pushed 'Tie-File-strict'.

In theory there is nothing wrong with this, but in practice it is asking
for trouble with collissions etc, not necessarily knowing who to ask about
a branch, etc. At $work we have a rule that all such branches should be
binomial, usually with the first component being the "owner" of the
branches name/username. Eg a small selection is as follows:

ap/baseincguard-old/3
ap/perlfunc-do
arc/smaller-toke
atoomic/installdocs-man
autarch/modernize-perlopentut
avar/no-UNIVERSAL-import-routine-TODO
avar/perldisthist

Most of our branches follow this convention, and we might even have had a
push check to prevent pushes that weren't binomial as we copied a lot of
our work rules to the perl5 git repo when we hosted it. If so then I assume
we lost this when we migrated to github.

Personally I think we should follow this convention, and ideally github
should enforce the rule.

Thoughts?

cheers,
Yves

-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About