Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jim Blandy" <jimb@red-bean.com>
To: "Elena Zannoni" <ezannoni@redhat.com>
Cc: "Daniel Jacobowitz" <drow@false.org>, gdb-patches@sourceware.org
Subject: Re: RFC: Readline 5.1 import
Date: Fri, 21 Apr 2006 01:16:00 -0000	[thread overview]
Message-ID: <8f2776cb0604201816u5624bd34if608227cbef5ec49@mail.gmail.com> (raw)
In-Reply-To: <17479.61920.803213.910287@localhost.redhat.com>

On 4/20/06, Elena Zannoni <ezannoni@redhat.com> wrote:
> We do already have a branch named FSF where the readline imports have
> been done before. The same branch has ben used for importing pristine
> versions of texinfo. It seems the people you have asked must not be
> used to track code from 3rd parties, and are willing to cut corners.

CVS vendor branches have some weird characteristics that I, at least,
have found hard to work with.  If someone feels using them isn't worth
the trouble, I don't think it follows that they're "cutting corners";
time spent on maintenance machinery that doesn't pay its way is time
not spent fixing bugs users actually see.


  reply	other threads:[~2006-04-21  1:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 18:00 Daniel Jacobowitz
2006-04-10 18:30 ` Elena Zannoni
2006-04-10 18:40   ` Daniel Jacobowitz
2006-04-10 18:54     ` Elena Zannoni
2006-04-10 18:57       ` Daniel Jacobowitz
2006-04-20 17:32         ` Daniel Jacobowitz
2006-04-20 20:43           ` Elena Zannoni
2006-04-21  1:16             ` Jim Blandy [this message]
2006-04-21 13:25               ` Elena Zannoni
2006-04-24 22:10             ` Daniel Jacobowitz
2006-05-01 13:56               ` Daniel Jacobowitz
2006-05-05 18:26                 ` Daniel Jacobowitz
2006-04-10 19:04 ` Eli Zaretskii

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=8f2776cb0604201816u5624bd34if608227cbef5ec49@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=drow@false.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sourceware.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