From: Michael Matz <matz@suse.de>
To: Tom de Vries <tdevries@suse.de>
Cc: dwz@sourceware.org, jakub@redhat.com
Subject: Re: [RFC 1/13][odr] Cover letter
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1912111550340.29201@wotan.suse.de> (raw)
In-Reply-To: <44919257-1313-ed65-fb88-43b377a9bb12@suse.de>
Hello,
On Wed, 11 Dec 2019, Tom de Vries wrote:
> > but would expand a little bit on
> > the explanations. For --odr I would add a sentence describing the effect
> > of applying the ODR rule (without going into too much detail), i.e.
> > mention that this causes type DIEs that have to be the same per C++ rules
> > (same name basically) to be more forcefully deduped. Also a
> > description of the two modes basic/link might be in order for the user to
> > make a meaningful choice; alteratively describe it as debug/development
> > option if the user isn't supposed to use it in regular use.
> >
>
> I've updated the man page entries with your suggestions.
>
> Better like this?
Yep.
Ciao,
Michael.
next prev parent reply other threads:[~2019-12-11 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Tom de Vries
2019-01-01 0:00 ` Michael Matz
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Michael Matz
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Michael Matz [this message]
2019-01-01 0:00 ` Tom de Vries
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=alpine.LSU.2.21.1912111550340.29201@wotan.suse.de \
--to=matz@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
--cc=tdevries@suse.de \
/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).