Commit 43f75bc1 authored by Jani Nikula's avatar Jani Nikula

TODO: remove TODO, handle bugs and feature requests on gitlab

The old TODO items have now been migrated to gitlab [1]. Remove
TODO.rst. Emphasize gitlab issues for bug reports and feature requests
in the documentation.

[1] https://gitlab.freedesktop.org/drm/maintainer-tools/issuesReviewed-by: 's avatarLucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Jani Nikula's avatarJani Nikula <jani.nikula@intel.com>
parent 6d47e41e
Pipeline #11854 passed with stages
in 46 seconds
......@@ -5,8 +5,9 @@
==========================
Please use the `dim-tools@lists.freedesktop.org`_ mailing list for
contributions, bug reports, and discussion about the tooling and
documentation. You may also file `issues`_ at the `project home page`_.
contributions, questions, and discussion about the tooling and documentation.
Please file `bug reports and feature requests`_ at the `project home page`_.
Please make sure your patches pass the build and self tests by running::
......@@ -16,6 +17,6 @@ Push the patches once you have an ack from :ref:`maintainers`.
.. _dim-tools@lists.freedesktop.org: https://lists.freedesktop.org/mailman/listinfo/dim-tools
.. _issues: https://gitlab.freedesktop.org/drm/maintainer-tools/issues
.. _bug reports and feature requests: https://gitlab.freedesktop.org/drm/maintainer-tools/issues
.. _project home page: https://gitlab.freedesktop.org/drm/maintainer-tools/
TODO
====
dim
---
- extract the integration tree logic and make it generally useful, maybe for a
drm-integration tree ...
- add option to check-patch to check stdin
- integrate ninja-check? Or too much checkers considered harmful?
https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2014-May/000554.html
- add patchwork Link: also after manually resolving conflicts in drm
apply-resolved
- allow dim rebuild-nightly to pull branches from local trees in dry-run mode.
This is useful to confirm a backmerge is indeed correct, by comparing the
resulting -nightly with the old one. Current the branch must be pushed out
first for rebuild-nightly to pick it up, which means the merge can't be
fixed any more.
- apply-resolved fails to add the Link: tag.
- Harvest and add Cc labels to all authors when tagging a branch
(ex: https://cgit.freedesktop.org/drm-misc/tag/?h=drm-misc-next-2018-03-21)
- Parse Cc labels from tag body and add as email headers when sending pull requests
qf
--
- get better at preventing and cleaning up a mess when switching branches
while there's still applied quilt patches around ...
- combine quilt annotate and git blame into one tool
- use the index a bit more to e.g. stage all applied quilt patches, then use
the output of git diff to refresh a quilt patch
- use git commit-tree and git write-tree in the setup code instead of the
current high-level hacks
- track/restore the topmost patch maybe?
- synchronize quilt notes in qf push and qf fetch
- switch patches/ over to worktree - those didn't exist yet when qf was
started, and integrate much better with git
- helper script to apply a git patch mbox, including naming the patch file and
all that
- try to figure out how to make quilt use git-style diffs, so avoid all the
nasty differences in diff output when regenerating patch files. Alternative:
Figure out how to make git apply-mbox as relaxed with applying slightly
misaligned patches as quilt - that would also remove the need to refresh
patches all the time.
......@@ -36,7 +36,6 @@ Contents:
CONTRIBUTING
MAINTAINERS
COPYING
TODO
Indices and tables
==================
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment