Re: [HACKERS] Re: HISTORY for 6.5.2
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] Re: HISTORY for 6.5.2 |
Дата | |
Msg-id | 15996.937317232@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Re: HISTORY for 6.5.2 (Bruce Momjian <maillist@candle.pha.pa.us>) |
Список | pgsql-hackers |
Bruce Momjian <maillist@candle.pha.pa.us> writes: >> This is *not* in 6.5.*, only 6.6. > I have: > RCS file: /usr/local/cvsroot/pgsql/src/interfaces/libpq/pqexpbuffer.c,v > Working file: src/interfaces/libpq/pqexpbuffer.c > head: 1.1 > Seems addition of text files shows up in all branches, which I guess > makes sense. No cause for alarm. I've noticed that cvs log seems a little bogus in its handling of branches, even though cvs status and cvs update know perfectly well what belongs to the local branch and what doesn't. If you say "cvs log" you get the "current" (tip revision's) log entries, even if you are in a directory that's been checked out with a sticky branch tag. If you say "cvs log -rBRANCH" you get the branch's log entries, but *only* those applied since the branch was split; there doesn't seem to be any way to get the full history as seen in this branch. And, as above, it's quite confusing about files that are not in the local branch at all. Dunno if the cvs folk consider these behaviors bugs or features, but they're definitely something to be wary of when working in a branch... regards, tom lane
В списке pgsql-hackers по дате отправления: