Getting Started

For getting started grab the latest dim (drm-intel-maintainer) script from:

There’s also a sample config file for ~/.dimrc:

The recommended way to setup dim is to simply clone it:

$ cd $DIM_PREFIX # defaults to ~/.src, or whatever you've set in your .dimrc
$ git clone

Plus, there’s bash completion in the same directory if you feel like using that. Run:

$ dim help

for tons of details about how this thing works. Also see the git repository specific pages for details on the patch merging process for each tree. Adjust your .dimrc to match your setup and then run:

$ dim setup

This expects that you have the maintainer-tools already checked out in $DIM_PREFIX/maintainer-tools. And by the way, if you have improvements for dim, see contributing.

If you have a account and plan to push things on one of the drm-xxx repos, you should use the ssh:// urls when adding a remote. Note that dim will ask you to add missing remotes automatically, and by default uses the ssh:// url format. To make these urls without login names work, you should add a new entry in ~/.ssh/config, if that’s not yet configured:

$ printf '\nHost\n\tUser <username>' >> ~/.ssh/config

You should now have a main repository for patch application. The directory corresponding to this repository is defined by DIM_REPO in your .dimrc. You should also have directories called maintainer-tools, drm-tip (for rebuilding the tree), and drm-rerere for some dim-internal book-keeping.

If someone else has pushed patches first resync using:

$ dim update-branches

Since dim supports lots of different branches in different repositories you first need to check out the right branch using:

$ dim checkout <branch>

Applying patches is done in the main repository with:

$ cat patch.mbox | dim apply-branch <branch>

This works like a glorified version of git apply-mbox and does basic patch checking and adds stuff like patchwork links of the merged patch. It is preferred to use the patch email file instead of the original patch file since it contains some interesting headers like the message ID. When you’re happy (remember that with a shared tree any mistake is permanent and there’s no rebasing) push out the new tree with:

$ dim push-branch <branch>

This will also rebuild a new drm-tip integration tree. For historical reasons there’s shortcut for the drm-intel specific branches for most of these commands.

If a commit that is already present in a branch has to be cherry-picked (e.g: a fix for drm-misc-fixes that is already in drm-misc-next), the dim tool must used as well instead of the git cherry-pick command. This can be done with:

$ dim cherry-pick <commit>

This will not only cherry-pick the commit but also add some metadata such as the cherry-picked commit SHA-1 hash. Also checks if there were any following commits in that branch that referenced the cherry-picked commit. This is useful to avoid missing any follow-up fixes for the commit being cherry-picked.

Please note that if there is no specific command available from dim then you can always use your every day tooling to get things done. For example, if a wrong patch was applied or you need to update commit message or fix anything else in the git repository, then just use git to do so as usual.

Please subscribe to the mailing list if you use dim.