Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Gnus overrides.texi and WEBHACKDEVEL (was: Revision 103117 on the Emacs trunk.)
Date: Sat, 05 Feb 2011 08:21:18 -0600	[thread overview]
Message-ID: <877hdebm01.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <m2hbcipr14.fsf@igel.home>

On Sat, 05 Feb 2011 14:08:55 +0100 Andreas Schwab <schwab@linux-m68k.org> wrote: 

AS> Eli Zaretskii <eliz@gnu.org> writes:
>> Also, overrides.texi is in the repository, but these two new rules
>> will overwrite it, and the modified overrides.texi could then easily
>> be committed by mistake as part of the next "bzr ci", thus propagating
>> a file with "@set WEBHACKDEVEL" to everyone else.  That's bad, I
>> think.

AS> It won't work when building outside srcdir anyway.

>> webhack:
>> $(MAKE) all MAKEINFO_OPTS="-DWEBHACKDEVEL --force -I$(emacsdir)"

AS> That should be

AS> 	$(MAKE) all MAKEINFO_OPTS="-DWEBHACKDEVEL $(MAKEINFO_OPTS)"

(I adjusted the Subject line so it's useful to Gnus developers and users
too)

That's what I wanted (and why I said overrides.texi was a hack :) except
the PDF and HTML targets are desired; I comitted a change to Gnus
accordingly to just do PDF for now.  Let me know what you think.

Now, overrides.texi is for Gnus manuals overrides: settings we may want
to propagate to all our manuals.  So I think it makes sense to have it,
just not the way I did it with shell redirection.  I renamed it to
gnus-overrides.texi and it can be used for things we want to use in all
the Gnus manuals in the future.  I hope that's OK with everyone; if not
it's easy enough to pull that include out.

Ted




  reply	other threads:[~2011-02-05 14:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05  9:35 Revision 103117 on the Emacs trunk Eli Zaretskii
2011-02-05  9:52 ` Katsumi Yamaoka
2011-02-05 11:47   ` Eli Zaretskii
2011-02-05 12:16     ` Katsumi Yamaoka
2011-02-07 18:29       ` Ted Zlatanov
2011-02-08  3:49         ` Eli Zaretskii
2011-02-08  8:00           ` Peter Münster
2011-02-08  8:28             ` Eli Zaretskii
2011-02-08  8:50               ` Andreas Schwab
2011-02-08  9:06               ` Peter Münster
2011-02-08  9:28                 ` Eli Zaretskii
2011-02-08 14:33           ` -DWEBHACKDEVEL for Gnus (was: Revision 103117 on the Emacs trunk.) Ted Zlatanov
2011-02-08 15:23             ` -DWEBHACKDEVEL for Gnus Peter Münster
2011-02-05 13:08     ` Revision 103117 on the Emacs trunk Andreas Schwab
2011-02-05 14:21       ` Ted Zlatanov [this message]
2011-02-05 15:12         ` Gnus overrides.texi and WEBHACKDEVEL Eli Zaretskii
2011-02-05 15:18           ` Ted Zlatanov
2011-02-05 15:39             ` Eli Zaretskii
2011-02-05 16:01               ` Ted Zlatanov
2011-02-07 19:06                 ` Eli Zaretskii
2011-02-07 19:19                   ` Ted Zlatanov
2011-02-07 19:47                   ` Eli Zaretskii
2011-02-06  6:49               ` Stephen J. Turnbull
2011-02-06 10:25                 ` Eli Zaretskii
2011-02-06 14:40                   ` Stephen J. Turnbull
2011-02-06 17:22                     ` Eli Zaretskii
2011-02-06 17:52                       ` Stephen J. Turnbull
2011-02-06 18:50                         ` Eli Zaretskii
2011-02-06 19:20                           ` Stephen J. Turnbull
2011-02-06 21:21                             ` Eli Zaretskii

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=877hdebm01.fsf_-_@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.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).