Re: git: uh-oh

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: git: uh-oh
Дата
Msg-id 7399.1283746186@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: git: uh-oh  (Michael Haggerty <mhagger@alum.mit.edu>)
Ответы Re: git: uh-oh  (Magnus Hagander <magnus@hagander.net>)
Re: git: uh-oh  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Michael Haggerty <mhagger@alum.mit.edu> writes:
> Tom Lane wrote:
>> I suspect what it's doing is attributing the branch creation to the user
>> who makes the first commit on the branch for that file.  In general I'd
>> expect that to give a reasonable result --- better than choosing a
>> guaranteed-to-be-wrong constant value anyway ;-)

> On the contrary, I prefer an obvious indication of "I don't know" to a
> value that might appear to be authoritative but is really just a guess.
>  It could be that one user copied the file verbatim to the branch and a
> second user changed the file as part of an unrelated change.

Hm, I see.

> The "default default" value for these commits is "cvs2svn" (in your case
> "cvs2git would probably be more appropriate), which I like because it
> makes it clearer than "pgsql" that the commit was generated as part of a
> conversion.

If we can set it to a value different from any actual committer name,
that would be a good thing to do.
        regards, tom lane


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

Предыдущее
От: Michael Haggerty
Дата:
Сообщение: Re: git: uh-oh
Следующее
От: KaiGai Kohei
Дата:
Сообщение: Re: leaky views, yet again