Skip to content
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.

Sign up for GitHub

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

Adapt to new naming convention. #105

Merged
merged 2 commits into from
Jul 15, 2013
Merged

Adapt to new naming convention. #105

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ef9bec9
Merge pull request #2 from cms-sw/gh-pages
ktf Jul 15, 2013
adea999
Change git addpkg / checkdeps to git cms-addpkg / cms-checkdeps.
ktf Jul 15, 2013
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions git-cms-addpkg.mdwn
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down Expand Up @@ -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
<develop>
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:
Expand All @@ -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?