Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@suse.com>
To: Thorsten Berger <thorsten.berger@rub.de>
Cc: Boris Kolpackov <boris@codesynthesis.com>,
	linux-kbuild@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	deltaone@debian.org, phayax@gmail.com,
	Eugene Groshev <eugene.groshev@gmail.com>,
	Sarah Nadi <nadi@ualberta.ca>, Mel Gorman <mgorman@suse.de>
Subject: Re: [RFC 0/3] kconfig: add support for conflict resolution
Date: Wed, 20 Oct 2021 08:57:34 -0700	[thread overview]
Message-ID: <YXA8biZ0kwoNSwW2@garbanzo> (raw)
In-Reply-To: <e397cd12-e9dc-a305-49b9-f5c6ac3ae10f@rub.de>

On Wed, Oct 20, 2021 at 04:37:49PM +0200, Thorsten Berger wrote:
> On 20.10.2021 14:25, Boris Kolpackov wrote:
> > Thorsten Berger <thorsten.berger@rub.de> writes:
> > 
> > > New UI extensions are made to xconfig with panes and buttons to allow users
> > > to express new desired target options, calculate fixes, and apply any of
> > > found solutions.
> > > 
> > > [...]
> > > 
> > > You can see a YouTube video demonstrating this work [2].
> > While the demo looks impressive, I wonder if you ran into many cases
> > where the number of solution and/or the number of fixes in a solution
> > is large (and therefore would be hard for a human to make a decision
> > about)?
> > 
> > My closest experience with something like this is aptitude and the
> > few times I tried to use it to solve package dependency issues were
> > futile because of that (i.e., large number of alternative solutions
> > and large number of changes in each solution).
> Thanks! BTW, I've opened a new thread, since the emails with the main
> patches didn't go through before (were too large) -- perhaps you can switch
> to that one.

Use git format-patch --subject-prefix="RFC v3" for your v3 series.

 Luis


      reply	other threads:[~2021-10-20 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 17:28 [RFC 0/3] kconfig: add support for conflict resolution Thorsten Berger
2021-10-19 17:32 ` [RFC 3/3] Simplify dependencies for MODULE_SIG_KEY_TYPE_RSA &, MODULE_SIG_KEY_TYPE_ECDSA Thorsten Berger
2021-10-20  1:32 ` [RFC 0/3] kconfig: add support for conflict resolution Randy Dunlap
2021-10-20  8:06   ` Thorsten Berger
2021-10-20 14:32     ` Randy Dunlap
2021-10-20 12:25 ` Boris Kolpackov
2021-10-20 14:37   ` Thorsten Berger
2021-10-20 15:57     ` Luis Chamberlain [this message]

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=YXA8biZ0kwoNSwW2@garbanzo \
    --to=mcgrof@suse.com \
    --cc=boris@codesynthesis.com \
    --cc=deltaone@debian.org \
    --cc=eugene.groshev@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mgorman@suse.de \
    --cc=nadi@ualberta.ca \
    --cc=phayax@gmail.com \
    --cc=thorsten.berger@rub.de \
    /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