Re: Managing multiple branches in git
От
Mark Mielke
Тема
Re: Managing multiple branches in git
Дата
Msg-id
4A257AAD.9030308@mark.mielke.cc
Ответ на
Re: Managing multiple branches in git (Alvaro Herrera)
Список
Дерево обсуждения
Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Greg Stark <greg.stark@enterprisedb.com>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Greg Stark <greg.stark@enterprisedb.com>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Bruce Momjian <bruce@momjian.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Stephen Frost <sfrost@snowman.net>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Stephen Frost <sfrost@snowman.net>
Re: Managing multiple branches in git "Markus Wanner" <markus@bluegap.ch>
Re: Managing multiple branches in git Greg Stark <stark@enterprisedb.com>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "Joshua D. Drake" <jd@commandprompt.com>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git Mark Mielke <mark@mark.mielke.cc>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git Dave Page <dpage@pgadmin.org>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Magnus Hagander <magnus@hagander.net>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git "Joshua D. Drake" <jd@commandprompt.com>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Dave Page <dpage@pgadmin.org>
Re: Managing multiple branches in git Dave Page <dpage@pgadmin.org>
Re: Managing multiple branches in git Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Managing multiple branches in git Robert Haas <robertmhaas@gmail.com>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Peter Eisentraut <peter_e@gmx.net>
Re: Managing multiple branches in git Greg Smith <gsmith@gregsmith.com>
Re: Managing multiple branches in git "Greg Sabino Mullane" <greg@turnstep.com>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Marko Kreen <markokr@gmail.com>
Re: Managing multiple branches in git Florian Weimer <fweimer@bfk.de>
Re: Managing multiple branches in git Andres Freund <andres@anarazel.de>
Re: Managing multiple branches in git Marko Kreen <markokr@gmail.com>
Re: Managing multiple branches in git Dave Page <dpage@pgadmin.org>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git "Markus Wanner" <markus@bluegap.ch>
Re: Managing multiple branches in git Alvaro Herrera <alvherre@commandprompt.com>
Re: Managing multiple branches in git "Markus Wanner" <markus@bluegap.ch>
Re: Managing multiple branches in git Andrew Dunstan <andrew@dunslane.net>
Re: Managing multiple branches in git Tom Lane <tgl@sss.pgh.pa.us>
Re: Managing multiple branches in git Aidan Van Dyk <aidan@highrise.ca>
Re: Managing multiple branches in git "David E. Wheeler" <david@kineticode.com>
Re: Managing multiple branches in git Marko Kreen <markokr@gmail.com>
Alvaro Herrera wrote:Mark Mielke wrote:I am curious about why an end user would really care? CVS and SVN both kept local workspace directories containing metadata. If anything, I find GIT the least intrusive of these three, as the .git is only in the top-level directory, whereas CVS and SVN like to pollute every directory.That's not the problem. The problem is that it is kept in the same directory as the checked out copy. It would be a lot more usable if it was possible to store it elsewhere.
I'm not following. CVS and SVN both kept such directories "in the checked out copy." Recall the CSV/*,v files?
As for storing it elsewhere - if you absolute must, you can. There is a --git-dir=GIT_DIR and --work-tree=GIT_WORK_TREE option to all git commands, and GIT_DIR / GIT_WORK_TREE environment variables.
I just don't understand why you care. If the CVS directories didn't bug you before, why does the single .git directory bug you now? I'm genuinely interested as I don't get it. :-)
Cheers,
mark-- Mark Mielke <mark@mielke.cc>
В списке pgsql-hackers по дате отправления