From: Jim Blandy <jimb@cygnus.com>
To: Stan Shebs <shebs@cygnus.com>
Cc: gdb@cygnus.com
Subject: Re: Retiring obsolete files
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <np3e4w3331.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <199901220026.QAA29779@andros.cygnus.com>
> Opinions? If no one objects, I will set this in motion for 4.18.
It sounds good to me.
How does this approach compare with making a new directory tree
gdb/obsolete? So gdb/config/victrola would get moved to
gdb/obsolete/config/victrola?
Is your sed script invertible? Someone resuscitating an old platform
would probably appreciate that. If the file contains any *//*
sequences to begin with, then I think it isn't. How about
sed -e 's,*,*x,g'
to deal with existing comments, and everything else stays the same?
After you've stripped off the "/* OBSOLETE " and " */" that were
guaranteed to be added to every line, then you know that
sed -e 's,*x,*,g'
will restore everything properly, even if there were "*x" sequences in
the code already.
prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 0:00 Stan Shebs
1999-04-01 0:00 ` Jim Blandy [this message]
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=np3e4w3331.fsf@zwingli.cygnus.com \
--to=jimb@cygnus.com \
--cc=gdb@cygnus.com \
--cc=shebs@cygnus.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