Re: [HACKERS] FYI: git worktrees as replacement for "rsync theCVSROOT"
От | Andrew Dunstan |
---|---|
Тема | Re: [HACKERS] FYI: git worktrees as replacement for "rsync theCVSROOT" |
Дата | |
Msg-id | ac296431-af58-ecc5-73dc-9de63651fe6f@2ndQuadrant.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] FYI: git worktrees as replacement for "rsync the CVSROOT" (Craig Ringer <craig@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] FYI: git worktrees as replacement for "rsync the CVSROOT"
|
Список | pgsql-hackers |
On 02/24/2017 02:36 AM, Craig Ringer wrote: > On 16 January 2017 at 05:01, Jim Nasby <Jim.Nasby@bluetreble.com> wrote: >> Not sure how many people still use [1], as referenced by our git wiki[2], >> but it appears git worktrees are a viable replacement for that technique. In >> short, if you're already in your checkout: >> >> git worktree add ../9.6 REL9_6_STABLE >> >> would give you a checkout of 9.6 in the ../9.6 directory. >> >> BTW, I learned about this from this "git year in review" article[3]. > Looks handy enough to merit adding to the Pg developer FAQ. Please? > > It looks cleaner than my current approach of doing a local clone or > re-cloning from upstream with a local repo as a --reference . > Does this do anythng different from the git contrib script git-new-workdir that I have been using for quite a long while? Essentially it symlinks a bunch of things from the old workdir to the new one. I copied the technique in the buildfarm's git_use_workdirs feature. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: