From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] readme.gentoo.eclass: Add a readme.gentoo_force_print_elog function to force elog printing
Date: Tue, 22 Jan 2013 09:07:01 +0100 [thread overview]
Message-ID: <1358842021.2064.55.camel@belkin4> (raw)
In-Reply-To: <CA+NrkpdW=fMumdn80MVDoe8MU7=D8wDBBpApNtSA2O3HLWgOfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
El mar, 22-01-2013 a las 08:16 +0100, Tomáš Chvátal escribió:
> 2013/1/21 Pacho Ramos <pacho@gentoo.org>:
> > This can be useful when, for example, doc contents are modified. You can
> > then rely on using REPLACING_VERSIONS in your ebuild to print messages
> > when people updates from versions using old docs
> >
> > Patch to review attached
> >
>
> Would'nt be better to just set some variable in the ebuild, rather
> than call function that touches empty file?
>
> Tom
>
>
I think it can be done in either way... but I don't see the advantage of
any over the other :/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-01-22 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 21:08 [gentoo-dev] readme.gentoo.eclass: Add a readme.gentoo_force_print_elog function to force elog printing Pacho Ramos
2013-01-22 7:16 ` Tomáš Chvátal
2013-01-22 8:07 ` Pacho Ramos [this message]
2013-01-22 9:33 ` Tomáš Chvátal
2013-01-22 18:37 ` Pacho Ramos
2013-01-22 18:42 ` Tomáš Chvátal
2013-01-24 20:33 ` Pacho Ramos
2013-01-24 20:42 ` Tomáš Chvátal
2013-01-24 21:39 ` Pacho Ramos
2013-02-01 14:32 ` Fabio Erculiani
2013-02-01 14:34 ` Fabio Erculiani
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=1358842021.2064.55.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox