From: Hans-Peter Nilsson <hp@bitrange.com>
To: Christian Groessler <chris@groessler.org>
Cc: binutils@sources.redhat.com, bonzini@gnu.org
Subject: Re: [PATCH]: missing trailing slash in toplevel makefile
Date: Mon, 15 Aug 2005 22:26:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0508151823530.36101@dair.pair.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0508152219220.536-100000@ds9.groessler.org>
On Mon, 15 Aug 2005, Christian Groessler wrote:
> Hi,
>
> pretty obvious.
Hm somewhat, but is it needed? ISTR things had changed such
that the slash isn't needed anymore. Did something break or was
it just spotted by code inspection?
brgds, H-P
next prev parent reply other threads:[~2005-08-15 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 20:23 Christian Groessler
2005-08-15 21:25 ` DJ Delorie
2005-08-16 20:47 ` Christian Groessler
2005-08-17 7:13 ` Paolo Bonzini
2005-08-17 15:54 ` Christian Groessler
2005-08-15 22:26 ` Hans-Peter Nilsson [this message]
2005-08-16 13:21 ` Christian Groessler
2005-08-16 13:29 ` Paolo Bonzini
2005-08-16 20:45 ` Christian Groessler
2005-08-16 14:23 ` Hans-Peter Nilsson
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=Pine.BSF.4.58.0508151823530.36101@dair.pair.com \
--to=hp@bitrange.com \
--cc=binutils@sources.redhat.com \
--cc=bonzini@gnu.org \
--cc=chris@groessler.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 read-only IMAP folder(s) and NNTP newsgroup(s).