Re: Managing multiple branches in git - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Managing multiple branches in git
Date
Msg-id 21376.1243985982@sss.pgh.pa.us
Whole thread Raw
In response to Re: Managing multiple branches in git  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Managing multiple branches in git  (Andres Freund <andres@anarazel.de>)
Re: Managing multiple branches in git  ("David E. Wheeler" <david@kineticode.com>)
Re: Managing multiple branches in git  (Stephen Frost <sfrost@snowman.net>)
Re: Managing multiple branches in git  (Mark Mielke <mark@mark.mielke.cc>)
Re: Managing multiple branches in git  ("Markus Wanner" <markus@bluegap.ch>)
Re: Managing multiple branches in git  (Greg Stark <stark@enterprisedb.com>)
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> Does that make sense?

Maybe, but it still seems messy, brute force, and error-prone.

I can't escape the feeling that we're missing something basic here.
It's allegedly one of git's great strengths that it allows you to easily
and quickly switch your attention among multiple development branches.
Well, so it does, if you haven't got any derived files to rebuild.
But rebuilding the Linux kernel is hardly a zero-cost operation,
so how have Linus and co failed to notice this problem?  There
must be some trick they're using that I haven't heard about, or
they'd not be nearly so pleased with git.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jeremy Kerr
Date:
Subject: [PATCH v2] Add bit operations util header
Next
From: Andres Freund
Date:
Subject: Re: Managing multiple branches in git