Re: Moving CVS files around?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Moving CVS files around?
Date: 2001-09-27 18:47:06
Message-ID: 200109271847.f8RIl6901147@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I'm considering moving s_lock.c from backend/storage/buffer, where it
> seems to make no sense, into backend/storage/lmgr which seems like a
> more logical place for it. However, the only way to do it that I know
> of is to "cvs remove" in the one directory and then "cvs add" a new copy
> in the other. That would lose the CVS log history of the file, or at
> least make it a lot harder to find. Is there a way to attach the past
> commit history to the file in its new location? Should I just do it and
> not worry about the history? Should I leave well enough alone?

I vote you just move it. It never made sense in /buffer to me either.
I always looked for it in lmgr first.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Martín Marqués 2001-09-27 20:55:36 Re: [PHP] [BUGS] PostgreSQL / PHP Overrun Error
Previous Message Neil Padgett 2001-09-27 18:42:42 Re: Spinlock performance improvement proposal