public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [maintainer-tools PATCH 30/30] qf: Use .dimrc to config and extend qf.
Date: Tue, 22 Aug 2017 15:49:00 +0300	[thread overview]
Message-ID: <87inhf4vk3.fsf@nikula.org> (raw)
In-Reply-To: <20170822124659.tcgm5nydkzf74yio@phenom.ffwll.local>

On Tue, 22 Aug 2017, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Aug 22, 2017 at 09:06:36AM +0200, Daniel Vetter wrote:
>> On Mon, Aug 21, 2017 at 01:11:20PM -0700, Rodrigo Vivi wrote:
>> > Soon we will need to extend qf for very specific
>> > usages of our internal maintenance and rebase bot.
>> > 
>> > So instead of creating yet another config file
>> > let's use the existent one.
>> > 
>> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> > Cc: Jani Nikula <jani.nikula@intel.com>
>> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> 
>> Now that qf list-aliases/cmds works, can we perhaps also rework the bash
>> completion to use that, like for dim?
>
> Another follow-up task would be to extract the qf help into qf.rst and add
> it to the sphinx build. For even more qf/dim consistency.

That's already done and pushed.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-08-22 12:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 20:10 [maintainer-tools PATCH 01/30] qf: Deprecate the use of qf without any subcommand Rodrigo Vivi
2017-08-21 20:10 ` [maintainer-tools PATCH 02/30] qf: Introduce subcommand and aliases Rodrigo Vivi
2017-08-21 20:10 ` [maintainer-tools PATCH 03/30] qf: Move "setup" from case to new subcommand Rodrigo Vivi
2017-08-21 20:10 ` [maintainer-tools PATCH 04/30] qf: Move "checkout" " Rodrigo Vivi
2017-08-21 20:10 ` [maintainer-tools PATCH 05/30] qf: Move "rebase" " Rodrigo Vivi
2017-08-21 20:10 ` [maintainer-tools PATCH 06/30] qf: Move "refresh" " Rodrigo Vivi
2017-08-21 20:10 ` [maintainer-tools PATCH 07/30] qf: Move "export" " Rodrigo Vivi
2017-08-21 20:10 ` [maintainer-tools PATCH 08/30] qf: Move "export-visualize" " Rodrigo Vivi
2017-08-21 20:10 ` [maintainer-tools PATCH 09/30] qf: Move "push" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 10/30] qf: Move "fetch" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 11/30] qf: Move "pull" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 12/30] qf: Move "stage" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 13/30] qf: Move "wiggle-push" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 14/30] qf: Move "resolved" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 15/30] qf: Move "apply" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 16/30] qf: Move "patch-amend" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 17/30] qf: Move "list-unused-patches" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 18/30] qf: Move "baseline" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 19/30] qf: Move "git" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 20/30] qf: Move "gitk" " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 21/30] qf: SC2006 - Fix one of shellcheck complains on qf Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 22/30] qf: SC2068 - Fix another shellcheck complain Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 23/30] qf: SC2053 - Fix another shellcheck complain: Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 24/30] qf: SC2155 - Fix another shellcheck complain Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 25/30] qf: SC2035 " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 26/30] qf: SC1091 " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 27/30] qf: SC2153 " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 28/30] qf: SC1083 " Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 29/30] qf: Add it to shellcheck part of make check Rodrigo Vivi
2017-08-21 20:11 ` [maintainer-tools PATCH 30/30] qf: Use .dimrc to config and extend qf Rodrigo Vivi
2017-08-22  7:06   ` Daniel Vetter
2017-08-22 12:46     ` Daniel Vetter
2017-08-22 12:49       ` Jani Nikula [this message]
2017-08-22  7:33   ` Jani Nikula
2017-08-22 18:16     ` Rodrigo Vivi
2017-08-23 15:13       ` Daniel Vetter
2017-08-23 17:23         ` [maintainer-tools PATCH] qf: Introduce .qfrc Rodrigo Vivi
2017-08-24  6:33           ` Daniel Vetter
2017-08-22  6:55 ` [maintainer-tools PATCH 01/30] qf: Deprecate the use of qf without any subcommand Daniel Vetter
2017-08-22  7:36   ` Daniel Vetter
2017-08-22 18:00     ` Rodrigo Vivi
2017-08-22 18:17   ` [PATCH] qf: Introduce subcommand and aliases Rodrigo Vivi
2017-08-22  7:34 ` [maintainer-tools PATCH 01/30] qf: Deprecate the use of qf without any subcommand Jani Nikula

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=87inhf4vk3.fsf@nikula.org \
    --to=jani.nikula@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox