From: Tim Waugh <twaugh@redhat.com>
To: "Éric Bischoff" <e.bischoff@noos.fr>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: new release soon
Date: Thu, 18 Apr 2002 12:24:00 -0000 [thread overview]
Message-ID: <20020418202443.X11579@redhat.com> (raw)
Message-ID: <20020418122400._DuqA2PWy8uoNB0ahV5TrLdCJvFYUhG6WmVnISvsrxo@z> (raw)
In-Reply-To: <200204181939.12883.e.bischoff@noos.fr>; from e.bischoff@noos.fr on Thu, Apr 18, 2002 at 07:39:12PM +0200
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On Thu, Apr 18, 2002 at 07:39:12PM +0200, Éric Bischoff wrote:
> On Thursday 18 April 2002 18:10, Tim Waugh wrote:
> > I am planning on making a new release of docbook-utils soon (within
> > the next week or two). I don't plan on changing much from what is
> > currently in CVS.
> >
> > Please take a look and shout if there is something wrong. To get a
> > tarball, use 'make -f Makefile.cvs', './configure', and 'make dist'.
>
> No, Tim, it's your responsibility to do the "make -f Makefile.cvs" _before_
> you do the tarballs.
I understand that---I'm just warning that I will make a release soon,
and that is how I will do it, so if you take a look at the result of
doing that you'll see something similar to the end product.
So take a look now, before I make the release.
(Do we need to do a pre-release for this? I'd rather not.)
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-04-18 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Tim Waugh
2002-04-18 9:40 ` Tim Waugh
2002-12-20 19:23 ` Mark Galassi
2002-04-18 10:47 ` Mark Galassi
2002-12-20 19:23 ` Tim Waugh
2002-04-18 12:34 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-04-18 10:39 ` Éric Bischoff
2002-12-20 19:23 ` Tim Waugh [this message]
2002-04-18 12:24 ` Tim Waugh
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=20020418202443.X11579@redhat.com \
--to=twaugh@redhat.com \
--cc=docbook-tools-discuss@sources.redhat.com \
--cc=e.bischoff@noos.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).