Re: git: uh-oh

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: git: uh-oh
Дата
Msg-id 10653.1283873416@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: git: uh-oh  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: git: uh-oh  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: git: uh-oh  (Michael Haggerty <mhagger@alum.mit.edu>)
Список pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Tue, Sep 7, 2010 at 17:07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Look for
>> � � � �This commit was manufactured by cvs2svn to create branch ...

> Ok, found a bunch of those (78 to be exact). And the issue with them
> is we want to change the commit author on them to be whomever made the
> first commit on the branch *after* that?

What I'd like is for those commits to vanish from the git log entirely.

In a practical sense, what you should probably do is for each file
mentioned in such a commit, cause the file's addition to the branch to
become part of the first regular commit on the branch that touched that
file.  In the CVS history, at least, there always is such a commit
(since we never did the cvs tag -b thing).  I am not sure though whether
the converted git history includes a touch of the file in that commit,
if the version committed into the branch is identical to what was on
HEAD.  Michael, can you comment on that point?
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Synchronization levels in SR
Следующее
От: Markus Wanner
Дата:
Сообщение: Re: Synchronization levels in SR