Hello, I have a few questions about the labeling operations. I tried to
enforce rules for the tags and branch folders but it didn't seem to work.
Here is what I have in my conf:
# Format of label names (tag or branch names) defined as
# regular expressions.
label_name => {
enabled => 1,
names => [
# Convention for official releases.
# For example:
# SCMBUG_RELEASE_0-2-7
#'^.+?_RELEASE_[0-9]+-[0-9]+-[0-9]+$',
'^ACM[0-9]+$',
# Convention for development builds.
# For example:
# SCMBUG_BUILD_28_added_a_policies_mechanism
#'^.+?_BUILD_[0-9]+_.+$',
'^D_ACM[0-9]+$',
# Convention for branches.
# For example:
# b_experimenting_with_policies_on_glue_side
#'^b_.+$',
'^B_ACM[0-9]+$',
# Convention for private developer tags. Uses
# the developer's initials (either 2 or 3).
# For example:
# p_kpm_prior_to_bug353_stabilization_fixes
'^p_[a-zA-Z][a-zA-Z]?[a-zA-Z]_.+$'
]
},
I'm not too familiar with the coding used for the default scmbug examples
but if someone could help me out a bit with expanations I would greatly
appreciate it .e.g the +$ ^ etc...
This is what I want in my repository:
tags/CM0100101
branches/B_CM0100101 or D_CM01000101
The only values that would change would be the last 3 which means something
like: B_CM0100[0-9][0-9][0-9] ?
Also from the example in the website:
http://files.mkgnu.net/files/scmbug/doc/latest_manual/html-multi/x210.html
it seems as though you are working from a working copy with the commit
statement, is the commit statement neccessary?
I just want to be able to do something like this from my client machine:
svn copy svn://repos/PRODUCT/trunk svn://repos/PRODUCT/branches/B_CM0100402
which was not enforced with the conf from above.
Any advice would be appreciated, thanks!
H.S
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
