public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug manual/13750] Do not build manuals in source directory
Date: Fri, 04 May 2012 11:25:00 -0000 [thread overview]
Message-ID: <bug-13750-131-mqp7JCmyW7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13750-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13750
Andreas Jaeger <aj at suse dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |aj at suse dot de
Resolution| |FIXED
AssignedTo|unassigned at sourceware |aj at suse dot de
|dot org |
--- Comment #1 from Andreas Jaeger <aj at suse dot de> 2012-05-04 11:24:19 UTC ---
This is fixed now in git with:
commit e3945c47bdac1149a1fec5d46bd567a248cd17b9
Author: Andreas Jaeger <aj@suse.de>
Date: Fri May 4 13:13:57 2012 +0200
Do not build manual in the source directory
[BZ #13750]
Build the manual in the build directory and
not anymore in the source directory.
I'll update install.texi now as well...
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-05-04 11:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 21:22 [Bug manual/13750] New: " jsm28 at gcc dot gnu.org
2012-02-25 1:58 ` [Bug manual/13750] " ppluzhnikov at google dot com
2012-05-04 11:25 ` aj at suse dot de [this message]
2012-05-14 20:05 ` aj at suse dot de
2014-06-26 14:38 ` fweimer at redhat dot com
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=bug-13750-131-mqp7JCmyW7@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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.
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).