all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 26170@debbugs.gnu.org
Subject: bug#26170: Bug #26170 Hunting: doc: Explanation of propagated-inputs unclear
Date: Tue, 3 Dec 2019 13:49:04 +0100	[thread overview]
Message-ID: <20191203124904.lotocvk7htki2ill@pelzflorian.localdomain> (raw)
In-Reply-To: <CAJ3okZ3=1GeVM6_hOWkUfc_rLODR=Lr7SF_6q=90NCO7vQvL2g@mail.gmail.com>

On Tue, Dec 03, 2019 at 01:14:05PM +0100, zimoun wrote:
> Dear Florian,
> 
> You report this bug [1] a couple of years ago about unclear
> explanations of the term propagated-inputs.
> […]
> Do you have already a patch? If no, do you plan to prepare one?
> 
> 
> Thank you in advance for any comments.
> 
> All the best,
> simon

Sorry I had totally forgotten about my bug report and do not have a
patch.  I do not have time at the moment or good knowledge of current
documentation and discussions, sorry.  I would be most happy if you
and/or others made patches for better explanations of profiles,
environments and propagated inputs.

Thank you for looking at / searching for old (but current) issues.

Regards,
Florian

  reply	other threads:[~2019-12-03 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19  7:03 bug#26170: documentation: Explanation of propagated-inputs unclear pelzflorian (Florian Pelz)
2019-12-03 12:14 ` bug#26170: Bug #26170 Hunting: doc: " zimoun
2019-12-03 12:49   ` pelzflorian (Florian Pelz) [this message]
2020-09-09 13:25     ` zimoun
2020-09-09 15:10       ` pelzflorian (Florian Pelz)
2020-09-09 15:45         ` zimoun
2020-09-16 10:37         ` Ludovic Courtès
2020-09-16 13:27           ` pelzflorian (Florian Pelz)
2020-09-17 19:45             ` Ludovic Courtès
2020-09-18  9:08               ` pelzflorian (Florian Pelz)

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=20191203124904.lotocvk7htki2ill@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=26170@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.