From adea9990958002f28749ebce4f6cf50ced92165b Mon Sep 17 00:00:00 2001 From: Giulio Eulisse Date: Mon, 15 Jul 2013 18:19:16 +0200 Subject: [PATCH] Change git addpkg / checkdeps to git cms-addpkg / cms-checkdeps. --- git-cms-addpkg.mdwn | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/git-cms-addpkg.mdwn b/git-cms-addpkg.mdwn index 17a73837865ca..ed94842d7e331 100644 --- a/git-cms-addpkg.mdwn +++ b/git-cms-addpkg.mdwn @@ -6,7 +6,7 @@ related: - { name: Topic Collector, link: https://cern.ch/cmsgit/cmsgit } - { name: Feedback, link: https://github.com/cms-sw/cmssw/issues/new } --- -# git-addpkg +# git-cms-addpkg One very common development workflow in CMS is to checkout a few packages from a base release in order to modify them. This is general done with the `addpkg` @@ -40,10 +40,10 @@ tags were a workaround to the limitation imposed by cost of tags in CVS. simply becomes: - git addpkg FWCore/Framework - git addpkg FWCore/Utilities + git cms-addpkg FWCore/Framework + git cms-addpkg FWCore/Utilities - git checkdeps -a + git cms-checkdeps -a For the above example the `git addpkg` helper will simply create for you a `.git/info/sparse-checkout` folder which contains: @@ -63,4 +63,3 @@ change. To hide a package, you will need to remove it from `.git/info/sparse-checkout` and run `git read-tree -mu HEAD` again. Note: do we need to provide a `git rmpkg` helper? -