This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Moving C to its own directory (was Re: ObjC tree inlining)
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: Phil Edwards <pedwards at disaster dot jaj dot com>, <gcc at gcc dot gnu dot org>
- Date: 20 Nov 2001 23:26:41 -0200
- Subject: Re: Moving C to its own directory (was Re: ObjC tree inlining)
- Organization: GCC Team, Red Hat
- References: <Pine.SOL.4.33.0111210115150.8599-100000@green.csi.cam.ac.uk>
On Nov 20, 2001, "Joseph S. Myers" <jsm28@cam.ac.uk> wrote:
> On Tue, 20 Nov 2001, Phil Edwards wrote:
>> What I meant was all that "revision 1" implies: 'log' and 'annotate'
>> are reset, for example.
>>
>> If the ,v files are moved, those commands continue to just work. Otherwise a
>> GCC hacker can only 'log' and 'annotate' back so far before being forced
>> to find an old checkout of the repo and repeating the work there.
> CVS annotate and log work just fine on files that have been cvs removed;
> try them on gcc/gcc.texi, for example. No old checkout is required.
Do you have any script handy that merges CVS annotate from two
different files, such that, if one line is marked as from revision 1,
it takes the line from the other? This would be necessary to give
developers the same amount of information from cvs annotate without
too much additional effort.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me