Re: git: uh-oh
От | Magnus Hagander |
---|---|
Тема | Re: git: uh-oh |
Дата | |
Msg-id | AANLkTi=bO0-VSacgx9nJQkUg+Ht6CRGD_T-bKtTqPZ6_@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: git: uh-oh (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: git: uh-oh
|
Список | pgsql-hackers |
On Tue, Sep 7, 2010 at 16:16, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Magnus Hagander <magnus@hagander.net> writes: >> On Tue, Sep 7, 2010 at 15:53, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> Michael Haggerty <mhagger@alum.mit.edu> writes: >>>> Somebody could use "git filter-branch" to make this change after the >>>> conversion, but I can't estimate how much work it would be. >>> >>> The conversion is already far better than I expected it would be when >>> we were first discussing this switch, so my inclination is to just live >>> with this one wart. > >> You're saying you don't "require" a fix on the latest issue here? Or >> should we spend some time trying to figure out if we can fix it with >> git-filter-branch? > > If you want to try, and it doesn't take much time, go for it. I was > just saying I wouldn't complain if we decide to live with it as-is. Ok. Do we have a way of identifying them - e.g. is it all the commits with a certain commit msg? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: