From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: [gnus git] branch master updated: m0-5-146-gc789890 =1= art: fix void-function on timer
Date: Fri, 19 Oct 2012 17:22:36 +0200 [thread overview]
Message-ID: <87lif2xz9f.fsf@dod.no> (raw)
In-Reply-To: <b4my5j2jyz3.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org>:
> Again, but why it's needed?
> gnus-art requires gnus, and gnus requires gnus-util.
Well... it's good practice to directly declare all dependencies you use,
even if you have them available through a transitive dependency.
prev parent reply other threads:[~2012-10-19 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1TPBiA-0002ZE-2b@quimby.gnus.org>
2012-10-19 14:52 ` Katsumi Yamaoka
2012-10-19 15:22 ` Julien Danjou
2012-10-19 15:31 ` Katsumi Yamaoka
2012-10-19 15:22 ` Steinar Bang [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=87lif2xz9f.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).