Remove CVS keywords from L1*

[nclopezo]

No description provided.

[cmsbuild]

A new Pull Request was created by @nclopezo (David Mendez) for CMSSW_7_0_X.

Remove CVS keywords from L1*

It involves the following packages:

L1TriggerConfig/L1GtConfigProducers
L1TriggerConfig/GctConfigProducers
L1Trigger/GlobalTrigger
L1TriggerConfig/L1ScalesProducers
L1Trigger/RPCTechnicalTrigger
L1Trigger/L1GctAnalyzer
L1TriggerConfig/L1GeometryProducers
L1TriggerConfig/L1CSCTPConfigProducers
L1Trigger/DTSectorCollector
L1Trigger/RegionalCaloTrigger
L1TriggerConfig/DTTPGConfigProducers
L1Trigger/GlobalCaloTrigger
L1Trigger/CSCTriggerPrimitives
L1TriggerConfig/CSCTFConfigProducers
L1Trigger/DTTraco
L1TriggerConfig/GMTConfigProducers
L1Trigger/DTTriggerServerTheta
L1TriggerConfig/DTTrackFinder
L1Trigger/DTUtilities
L1Trigger/RPCTrigger
L1Trigger/DTTrigger
L1Trigger/L1ExtraFromDigis
L1TriggerConfig/RCTConfigProducers
L1TriggerOffline/L1Analyzer
L1TriggerConfig/RPCTriggerConfig
L1Trigger/CSCTrackFinder
L1Trigger/TextToDigi
L1Trigger/DTTrackFinder
L1Trigger/GlobalTriggerAnalyzer
L1Trigger/DTBti
L1Trigger/DTTriggerServerPhi
L1Trigger/GlobalMuonTrigger

@mulhearn can you please review it and eventually sign? Thanks.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.

[ktf]

There are a few "$Date$ which should be removed as well.

[mulhearn]

Yes, I see there are still some $Date$ tags that haven't been removed. Will David make the change?

[ktf]

I hope so, but maybe tomorrow.

[ktf]

No particular reason to wait actually. We can have a smaller request tomorrow
to handle the rest. Unless you object I would just merge it.

[mulhearn]

OK I am attempting to merge and build it now...

[mulhearn]

This is taking forever, at this last line, any idea what is going on?

mulhearn@lxplus0378>cmsrel CMSSW_7_0_0_pre2
mulhearn@lxplus0378>cd CMSSW_7_0_0_pre2/src/
mulhearn@lxplus0378>cmsenv
mulhearn@lxplus0378>git cms-addpkg FWCore/Version
No release tags specified, using default CMSSW_7_0_0_pre2.
You are on branch CMSSW_7_0_X
Checking out FWCore/Version in tag CMSSW_7_0_0_pre2.
Cloning into '/afs/cern.ch/work/m/mulhearn/relval/take2/CMSSW_7_0_0_pre2/src'...
remote: Counting objects: 1443, done.
remote: Compressing objects: 100% (360/360), done.
remote: Total 532 (delta 446), reused 247 (delta 169)
Receiving objects: 100% (532/532), 75.58 KiB | 0 bytes/s, done.
Resolving deltas: 100% (446/446), completed with 407 local objects.
Branch from-CMSSW_7_0_0_pre2 set up to track remote branch CMSSW_7_0_X from official-cmssw.
Switched to a new branch 'from-CMSSW_7_0_0_pre2'
HEAD is now at 631bb66 Merge pull request #252 from ianna/geometry-data-xml-description
mulhearn@lxplus0378>git checkout -b mulhearn-validation
Switched to a new branch 'mulhearn-validation'
mulhearn@lxplus0378>git cms-merge-topic nclopezo:remove-cvs-keywords-from-l1
No release tags specified, using default CMSSW_7_0_0_pre2.
You are on branch CMSSW_7_0_X
Checking out FWCore/Version in tag CMSSW_7_0_0_pre2.
From .

• [new ref] -> merge-attempt
  remote: Counting objects: 1110, done.
  remote: Compressing objects: 100% (430/430), done.
  remote: Total 616 (delta 515), reused 284 (delta 183)
  Receiving objects: 100% (616/616), 164.21 KiB | 0 bytes/s, done.
  Resolving deltas: 100% (515/515), completed with 445 local objects.
  From https://github.com/nclopezo/cmssw
• [new branch] remove-cvs-keywords-from-l1 -> nclopezo/remove-cvs-keywords-from-l1
  Switched to branch 'merge-attempt'

[mulhearn]

It seems I got the entire CMSSW repo when I used cms-merge-topic. What did I do wrong?

[mulhearn]

Sorry, new guy here: so am I supposed to have my own build of cms_sw:CMSSW_7_0_X built, and then just test these changes against it? Or is there some way to select out only the packages listed above from nclopezo:remove-cvs-keywords-from-l1 and compile against e.g. CMSSW_7_0_0_pre2?

Or am I just supposed to approve this because it only changed comments ;-)

[nclopezo]

Hi @mulhearn

You can use git cms-merge-topic 661, to get the changes on this pull request and test it.

I updated my pull request deleting the $Date$ tags. I am testing that it compiles here:

https://cmssdt.cern.ch/jenkins/job/Pull-Request-Integration/ARCHITECTURE=slc5_amd64_gcc472/321/console

[nclopezo]

As I see in the logs, everything compiled.

[cmsbuild]

Pull request #661 was updated. Signatures reset, please check and sign again.

[mulhearn]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next IBs unless changes or unless it breaks tests.

[mulhearn]

Thanks for doing the compile check on Jenkins and posting the log. If I wanted to compile a topic like this myself, e.g. for additional testing, is there a way I have access to the daily builds to compile against, or are those only available on Jenkins?

[nclopezo]

Hi @mulhearn

If you wanted to test on CMSSW_7_0_X_2013-08-29-1400 for example, you can run

cmsrel CMSSW_7_0_X_2013-08-29-1400

instead of

cmsrel CMSSW_7_0_0_pre2

and then

cmsenv
git cms-merge-topic 661
etc...

[mulhearn]

Oh! I didn't see these in "scram list CMSSW" because of different architecture... Thanks!