public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: palves@redhat.com, Paul_Koning@dell.com,
	gdb-patches@sourceware.org, stan@codesourcery.com
Subject: Re: gdb.texinfo is getting too big
Date: Fri, 01 Nov 2013 19:57:00 -0000	[thread overview]
Message-ID: <83bo23c2tx.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22RAp0Nda-_7f5SgWKADUD52gR-VV1J-sNTyWXweEc74bg@mail.gmail.com>

> Date: Fri, 1 Nov 2013 12:37:53 -0700
> From: Doug Evans <dje@google.com>
> Cc: Paul Koning <Paul_Koning@dell.com>, Eli Zaretskii <eliz@gnu.org>, 
> 	gdb-patches <gdb-patches@sourceware.org>, Stan Shebs <stan@codesourcery.com>
> 
> If people are ok with logical grouping units it's fine with me.
> One fear I have is a protracted discussion on the groupings.
> 
> I do like the idea of splitting out pieces that are easy to split out.
>   E.g., RSP, Python, maybe a few others.
> 
> How about starting with that?

Go for it.

  reply	other threads:[~2013-11-01 19:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 20:06 Doug Evans
2013-10-14 20:10 ` Eli Zaretskii
2013-10-14 20:26   ` Doug Evans
2013-10-15  2:44     ` Eli Zaretskii
2013-10-16 18:55       ` Doug Evans
2013-10-16 19:01         ` Eli Zaretskii
2013-10-16 19:52           ` Pedro Alves
2013-10-16 20:06             ` Eli Zaretskii
2013-10-16 20:10               ` Paul_Koning
2013-10-16 21:41                 ` Pedro Alves
2013-11-01 19:37                   ` Doug Evans
2013-11-01 19:57                     ` Eli Zaretskii [this message]
2013-10-16 21:29               ` Pedro Alves
2013-10-16 20:07       ` Stan Shebs

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=83bo23c2tx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Paul_Koning@dell.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=stan@codesourcery.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).