git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Three-tiered VM development setup with support for branch switching

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 20, 2010, 08:37 UTC
Message-ID
<AANLkTilIhuE06gVSO8cM_iLtixxBUX7DxrSlUbaCvmUs@mail.gmail.com>
In-Reply-To
<AANLkTinQJLsS6N_d2hsfwbibEuKiUHi9FAnrb5K4Frih@mail.gmail.com>
On Thu, May 20, 2010 at 00:59, Burke Cates <burke.cates@gmail.com> wrote:
Show 12 quoted lines
> The only solution I can think of involves ripping the branch out of
> the refspec that is passed to the hook and using that to call checkout
> and pull (or possibly a checkout -b --track newbranch if I dont have
> the branch locally on prime). I feel like this is a pretty nasty hack,
> but I might be missing something completely that would make this sort
> of setup much easier to pull off.
> What I'm trying to pull off here is this: devs can code at their
> workstations with whatever tools they want, and push changes to the
> VM's with git. Hooks will be used to initiate makes for testing and
> for pushing changes to other nodes in the test-cluster (who will have
> the same make hook). The only obstacle at this point is the branch
> switching.

If I'm not mistaken the plumbing commands like git-commit-tree allow you to make commits without switching branches. I.e. they just record raw data in the repository and don't care about your checkout.

Previous: Burke Cates
Message 2 of 2 in “Three-tiered VM development setup with support for branch switching”
  1. Burke CatesMay 20, 2010
  2. Ævar Arnfjörð BjarmasonMay 20, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.