All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: [PATCH 2/3] dim: Review subcommand docs
Date: Mon, 27 Mar 2017 10:45:45 +0200	[thread overview]
Message-ID: <20170327084546.4711-2-daniel.vetter@ffwll.ch> (raw)
In-Reply-To: <20170327084546.4711-1-daniel.vetter@ffwll.ch>

Inspired by Jani's efforts to clean this up and structure it better.

Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
 dim.rst | 20 ++++++++++++++------
 1 file changed, 14 insertions(+), 6 deletions(-)

diff --git a/dim.rst b/dim.rst
index 2f8fda8c42a7..be541d80ec7e 100644
--- a/dim.rst
+++ b/dim.rst
@@ -283,7 +283,9 @@ any changes with git add -u and continues the rebase.
 apply-resolved
 --------------
 Compile-test the current tree and if successfully resolve a
-confilicted git am. Also runs the patch checker afterwards.
+conflicted git am. Also runs the patch checker afterwards.
+
+FIXME: Forgets to add the Link: tag.
 
 create-branch *branch* [*commit-ish*]
 -------------------------------------
@@ -299,9 +301,8 @@ Remove the given topic branch.
 
 create-workdir (*branch* | all)
 -------------------------------
-Create a separate workdir for the branch with the given name (requires that
-git-new-workdir from git-core contrib is installed), or for all branches if
-"all" is given.
+Create a separate workdir for the branch with the given name, or for all
+branches if "all" is given.
 
 for-each-workdir|fw *command*
 -----------------------------
@@ -313,8 +314,8 @@ COMMANDS FOR MAINTAINERS
 
 cherry-pick *commit-ish* [*git cherry-pick arguments*]
 ------------------------------------------------------
-Improved git cherry-pick version which also scans drm-tip picked, too. In
-dry-run mode/-d only the patch list is generated.
+Improved git cherry-pick version which also scans drm-tip for additional
+cherry-pick candidates. In dry-run mode/-d only the patch list is generated.
 
 cherry-pick-fixes
 -----------------
@@ -366,6 +367,13 @@ opened.
 Also checks that the drm-intel-fixes|-next-queued are fully
 merged into drm-tip to avoid operator error.
 
+update-next-continue
+--------------------
+
+When **update-next** fails to push the special release commit (because it raced with
+another committer) rebase and push manually, and then continue using this
+command.
+
 tag-next
 --------
 Pushes a new tag for the current drm-intel-next state after checking that the
-- 
2.11.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-27  8:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  8:45 [PATCH 1/3] drm: Document maintainer duties Daniel Vetter
2017-03-27  8:45 ` Daniel Vetter [this message]
2017-03-27  8:49   ` [PATCH 2/3] dim: Review subcommand docs Daniel Vetter
2017-03-28  9:24   ` Jani Nikula
2017-03-27  8:45 ` [PATCH 3/3] dim: Backronym Daniel Vetter
2017-03-28  9:27   ` Jani Nikula
2017-04-03 10:59 ` [PATCH 1/3] drm: Document maintainer duties Eric Engestrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170327084546.4711-2-daniel.vetter@ffwll.ch \
    --to=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.