- Aug 03, 2017
-
-
Instead of listing branches and grepping for the current branch, simply read the name of the current branch and compare. Suggested-by:
Daniel Vetter <daniel.vetter@intel.com> Signed-off-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
The new apply and push commands are shorthands for applying patches to and pushing the current branch, respectively. v2: use git symbolic-ref to find current branch (Daniel Vetter) Signed-off-by:
Thierry Reding <treding@nvidia.com> [danvet: Fixup dim.rst as per Jani's review.] Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
Simona Vetter authored
mtime is when the file contents last changed, ctime when attributes in the inode last changed. We want the former. For some reason ctime in my rr-cache is always very recent. Acked-by:
Jani Nikula <jani.nikula@linux.intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
Simona Vetter authored
It's a bit silly to have to spec both -d and -f to see what dim would all complain about. And dry-run should never cause bad side-effects. Acked-by:
Jani Nikula <jani.nikula@linux.intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- Jul 26, 2017
-
-
Simona Vetter authored
Somehow a few formatting issues crept in that rst complained about in commit 7b414ba9e7aa75fc4dff6597036ff758031b9bdf (HEAD -> maintainer-tools) Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Thu Jul 20 21:28:12 2017 +0200 drm-intel.rst: Fix formatting Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Acked-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
Add checks for author and committer sign-off-by. Add a check for "Link" tag added by dim apply-branch. Use real names for people with many different email addresses. Signed-off-by:
Benjamin Gaignard <benjamin.gaignard@linaro.org> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- Jul 24, 2017
-
-
Simona Vetter authored
There's a failure mode I didn't take into account: 1. You start a dim rebuild-tip, and update your rr-cache. Because you didn't push for a while, this adds some really old files (but with today's timestamp). 2. 2nd person finished their dim rebuild-tip and garbage-collects the old rr-cache entries. 3. We get to commit_rr_cache, and the first thing the script does is update the rr-cache branch, which deletes the old entries. 4. Then we copy them over again, because their timestamp is fresh. 5. The filtering doesn't catch them, because git ls-files doesn't list them (they're deleted files after all). 6. They get re-added right away. I think this is what happend today between Chris and Imre, and resulted in a bit of confusion. I think if we pull only after copying this would be avoided, since the pull would delete the files the 2nd person gc'ed in step 2, and so prevents them from getting re-added. Worst case there's a functional conflict and the pusher needs to clean up the mess. Reviewed-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
Simona Vetter authored
Oops. It caused some concerns from people running dim rebuild-tip. v2: Drop misplaced changes I forgot to remove (Imre). Acked-by:
Imre Deak <imre.deak@linux.intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
Imre Deak authored
The output of git pull into the rr-cache branch isn't really interesting, so suppress it like during the rest of rr-cache branch maintenance commands. Cc: Jani Nikula <jani.nikula@intel.com> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by:
Imre Deak <imre.deak@intel.com> Acked-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- Jul 20, 2017
-
-
This patch adds a flowchart to the drm-misc documentation to help committers decide which branch is most appropriate for a given patch. Signed-off-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- Jul 18, 2017
-
-
Jani Nikula authored
The refactoring dropped a cd to the drm-rerere dir, leading to "cp: cannot stat 'rr-cache/*': No such file or directory" on dim ub. Reported-by:
Archit Taneja <architt@codeaurora.org> Fixes: 599eb3db ("dim: Move all rerere updating into helpers") Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Sean Paul <seanpaul@chromium.org> Reviewed-by:
Daniel Vetter <daniel.vetter@ffwll.ch> Tested-by:
Archit Taneja <architt@codeaurora.org> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
- Jul 17, 2017
-
-
Simona Vetter authored
http: gets a "301 moved permanently" reply. Reported-by:
Paul Menzel <paulepanter@users.sourceforge.net> Cc: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by:
Paul Menzel <paulepanter@users.sourceforge.net> Acked-by:
Jani Nikula <jani.nikula@intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- Jul 14, 2017
-
-
Simona Vetter authored
The problem is that we have a distributed cache - every committer has a copy. Which means even just a slight clock skew will make sure that a naive gc algorithm results in lots of thrashing around. To fix this add a huge hysteresis: Only add files newer than 1 day, and only remove them when older than 60 days. As long as people have reasonable accurate clocks on their machines this should work. A different problem is that we can't use filesystem timestamps (and hence can't use git rerere gc): When someone comes back from vacations and updates git rerere, all the files will have current timestamps, even when they've been pushed out weeks ago. To fix that, use the git log to judge old files to remove. Also, remove old files before adding new ones, to avoid confusion. Also, we need to teach the cp -r to preserve timestamps, otherwise this won't work. v2: Use git log to remove old files. v3: Remove the debug uncommenting (Sean). v4: Split out code movement and explain better what's going on (Jani). Reviewed-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
Simona Vetter authored
Just prep work. Reviewed-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- Jul 12, 2017
-
-
Maarten Lankhorst authored
This commit will take the topmost commit and add all cc's from get_maintainer.pl, it is useful for adding cc's to an entire patch series touching multiple drivers, to add the right cc to each one. Signed-off-by:
Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Acked-by:
Daniel Vetter <daniel.vetter@ffwll.ch> [mlankhorst: Rewrite commit message based on Jani's feedback] Acked-by:
Jani Nikula <jani.nikula@linux.intel.com>
-
- Jul 10, 2017
-
-
Rodrigo Vivi authored
All process related docs has moved to the new "process" folder, but also all .txt migrated to .rst as well. However let's link to final generated .html instead of .rst Ideally .rst would referrence .rst with :ref:`` but since these documentation are different repository we cannot link like this. However the main usage is through the compiled html pages and since we already reference another .html here so let's use our daily compiled doc. v2: squashed drm-intel: Link to .html instead of .rst Signed-off-by:
Rodrigo Vivi <rodrigo.vivi@intel.com> Acked-by:
Jani Nikula <jani.nikula@intel.com>
-
- Jul 06, 2017
-
-
Rodrigo Vivi authored
I noticed when resolving a conflict that reappeared. Signed-off-by:
Rodrigo Vivi <rodrigo.vivi@intel.com> Reviewed-by:
Jani Nikula <jani.nikula@intel.com>
-
- Jun 28, 2017
-
-
Simona Vetter authored
- Subcommands without subshell is nice, except it can break worktree setups: Branch specific commands want to run in the worktree, general commands like dim_cite switch back to the main directory. Tears ensue (or well, some cryptic complaint from git that cherry-pick --abort failed because there's no cherry-pick in progress). Run it in a subshell. Not sure we need a general fix to make this more robust. - Document commands a bit better. Cc: Jani Nikula <jani.nikula@linux.intel.com> Acked-by:
Jani Nikula <jani.nikula@linux.intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- Jun 19, 2017
-
-
The autogenerated driver date update patch doesn't have a r-b tag for obvious reasons, which gets caught up in the new r-b/a-b check in dim push-branch. Hack around this. Note this only overrides the dim checks, it's still a ff-only git push (the -f for that needs to be added as a push-branch parameter). Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
- May 29, 2017
-
-
Summarize the following discussion on dri-devel: "dim has you covered for this, in case you've rolled forward but Dave hasn't yet, you can regenerate against linus upstream branch for a cleaner pull (but still warn Dave ofc): $ dim pull-request drm-misc-next origin/master" (Daniel) "FWIW this is what I've always done with drm-intel-fixes." (Jani) "As long as I'm warned in the pull request I often fast forward to the base if my tree is clean, just to avoid the pull request having noise in it." (Dave) Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Jani Nikula <jani.nikula@linux.intel.com> Cc: Sean Paul <seanpaul@chromium.org> Cc: Dave Airlie <airlied@redhat.com> Signed-off-by:
Lukas Wunner <lukas@wunner.de> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- May 24, 2017
-
-
Simona Vetter authored
We can't check this when applying (since r-b/a-b tags often get added afterwards), but we can check this when pushing. This only looks at patches authored by the pusher. Also update the docs to highlight that review requirements hold especially also for bugfixes. v2: committer instead of committer (Sean/Chris). Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com> Cc: Lukas Wunner <lukas@wunner.de> Cc: Alex Deucher <alexander.deucher@amd.com> Cc: Christian König <deathsimple@vodafone.de> Cc: Sean Paul <seanpaul@chromium.org> Acked-by:
Sean Paul <seanpaul@chromium.org> Acked-by:
Jani Nikula <jani.nikula@linux.intel.com> Reviewed-by:
Lukas Wunner <lukas@wunner.de> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- May 08, 2017
-
-
In the merge timeline, remove the misc-next ~> drm-next merges while the merge window is active, and during rc1. Pulls should only be requested between rc2 and rc5. Signed-off-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- May 04, 2017
-
-
Each pull request is accompanied by a summary that is stored in the git tag from which it is generated. These summaries all share the same template with headers classifying changes to UAPI, Cross-subsystem, Core, and Drivers. This patch adds this template to the tag summary automatically in dim pull-request. Changes in v2: - Tweaked the template var name s/PULL/TAG/ (Daniel) Changes in v3: - Use git tag -F- to ingest template (Jani) - Tweak naming/comments again to hopefully clarify things (Jani) Signed-off-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
- Apr 18, 2017
-
-
Add a bit more colour to the -misc branch explanations, and add a merge timeline similar to the chart used in drm-intel. Signed-off-by:
Sean Paul <seanpaul@chromium.org> Reviewed-by:
Daniel Stone <daniels@collabora.com> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- Apr 07, 2017
-
-
Along with a recipe for creating a topic branch and sending a pull request from it. Signed-off-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
- Apr 05, 2017
-
-
Simona Vetter authored
This probably explains our fun today - remove-branch only removed the branch, but didn't push out the nightly.conf change. Acked-by:
Jani Nikula <jani.nikula@intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
Simona Vetter authored
We've just had some fun with a branch being deleted, but not immediately noticed because the remote tracking branch was still there. Make sure we catch such fumbles faster in the future. Acked-by:
Jani Nikula <jani.nikula@intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
This fixes `make check` when dim is not configured. Signed-off-by:
Eric Engestrom <eric.engestrom@imgtec.com> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Signed-off-by:
Eric Engestrom <eric.engestrom@imgtec.com> Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Simona Vetter authored
I butchered the tagging when implementing Jani's idea for fallback-tags in: commit c0c0d0c3 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Tue Mar 21 10:08:01 2017 +0100 dim: Stop force-pushing tags Cc: Jani Nikula <jani.nikula@intel.com> Acked-by:
Jani Nikula <jani.nikula@intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- Apr 04, 2017
-
-
Jani Nikula authored
The functions have been added kind of in the middle at some point. Clean it up. Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Jani Nikula authored
Reserve the middle part of the script for function and alias definitions only. Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Jani Nikula authored
It's rather obnoxious to exit in the middle of something just because you haven't updated the script. Only issue a warning. Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Jani Nikula authored
Signed-off-by:
Jani Nikula <jani.nikula@intel.com>
-
Simona Vetter authored
Somehow fell apart again in testing, let's do the same thing as with apply-branch, where we also apply the Link: after the sob is added. Cc: Jani Nikula <jani.nikula@linux.intel.com> Acked-by:
Jani Nikula <jani.nikula@intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
Simona Vetter authored
Don't fire up an editor by default. Requested by Jani. Cc: Jani Nikula <jani.nikula@intel.com> Acked-by:
Jani Nikula <jani.nikula@intel.com> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
Instead of hardcoding ~/tmp in dim (and failing when it doesn't exist), use mktemp to create the pull-request mail file. Signed-off-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@ffwll.ch>
-
Simona Vetter authored
Does a few sanity checks to avoid common gotchas: - make sure the backmerge is in drm-tip already - check that git rerere resolves all conflict, and cuation if not - merge commit template. v2: Spelling fix (Sean) Cc: Sean Paul <seanpaul@chromium.org> Acked-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- Apr 03, 2017
-
-
Simona Vetter authored
I think the initial experiment worked fairly well, and the kickstarting of a review (well, ack/best practices really) market seems to work ok-ish too. I think we can try to make it (slowly) scale to more drivers, with driver teams interested in being part of drm-misc. I do think we need to be careful though, to make sure we don't overstretch the review/mentoring bandwidth and can improve process&tooling as we go. v2: Spelling fix (Jani). Cc: Sumit Semwal <sumit.semwal@linaro.org> Cc: Gustavo Padovan <gustavo@padovan.org> Cc: Jani Nikula <jani.nikula@linux.intel.com> Acked-by:
Jani Nikula <jani.nikula@linux.intel.com> Cc: Sean Paul <seanpaul@chromium.org> Cc: Archit Taneja <architt@codeaurora.org> Cc: Gerd Hoffmann <kraxel@redhat.com> Cc: Boris Brezillon <boris.brezillon@free-electrons.com> Acked-by:
Boris Brezillon <boris.brezillon@free-electrons.com> Cc: Neil Armstrong <narmstrong@baylibre.com> Cc: Mark Yao <mark.yao@rock-chips.com> Cc: Eric Anholt <eric@anholt.net> Cc: Shawn Guo <shawnguo@kernel.org> Acked-by:
Shawn Guo <shawnguo@kernel.org> Cc: Dave Airlie <airlied@redhat.com> Acked-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-
- Mar 30, 2017
-
-
Simona Vetter authored
I'm getting real lazy, let's start scripting this. Very rough draft, but adds a Link: (patchwork tracks pull requests too, maybe we'll start CI-ing them too), and sob line. In the future we might add more checks here ... v2: Review from Jani: - Move abbrevation into my own .dimrc - Drop shift, we don't use $@ Signed-off-by:
Daniel Vetter <daniel.vetter@intel.com>
-