Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: MI docs: remove historic note
Date: Wed, 29 Nov 2006 18:58:00 -0000	[thread overview]
Message-ID: <200611292157.37913.ghost@cs.msu.su> (raw)
In-Reply-To: <uodqqay9y.fsf@gnu.org>

On Wednesday 29 November 2006 21:44, Eli Zaretskii wrote:
> > From:  Vladimir Prus <ghost@cs.msu.su>
> > Date:  Wed, 29 Nov 2006 18:52:31 +0300
> >
> > > Please just enclose the text in @ignore..@end ignore, instead of
> > > removing it altogether.  If no one complains in a couple of GDB
> > > releases, we will later remove it.
> >
> > Why is it better than removing? The text is there in CVS in case we need
> > to resurrect it.
>
> There's no useful way to grep the CVS repository for a version that
> had some specific text, especially if you don't remember the text
> accurately enough, and there's no record in anything like "cvs
> annotate" for when some text was deleted.  Checking out version after
> version looking for something I remember only vaguely is not my idea
> of fun.
>
> So resurrecting it will not be easy.  Therefore, I'd like to be
> reasonably sure no one wants it back for quite some time.  I hope you
> understand and don't object.

I certainly don't object -- I was just wondering about the best technical 
solution. I'll add @ignore later today -- I assume posting a separate patch 
is not required?

- Volodya


  reply	other threads:[~2006-11-29 18:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 14:38 Vladimir Prus
2006-11-15 18:23 ` Eli Zaretskii
2006-11-29 15:54   ` Vladimir Prus
2006-11-29 18:44     ` Eli Zaretskii
2006-11-29 18:58       ` Vladimir Prus [this message]
2006-11-29 19:11         ` 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=200611292157.37913.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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