Lines Matching refs:a

3 **HACK** in a **S**peedy **A**ccess **W**orkspace
7 …u have a large multi-gigabyte codebase spread out through multiple git projects it can take a long…
8 lets you split off a clean workspace in seconds. It does so by only copying git projects that you
9 …are read-only bind mounts. This lets you build without cloning the full codebase to a new location!
13 …ance numbers for creating a hacksaw workspace using as a codebase the AOSP master branch as of 202…
15 * Create a new Hacksaw workspace
19 * Remove a Hacksaw workspace with no edits or build artifacts.
22 * Create a new Hacksaw workspace and edit build/make project.
26 * Create a new Hacksaw workspace and edit frameworks/base project.
30 As you can see, the time it takes to set up a new hacksaw workspace is proportional to
32 to create a workspace using a full repo sync with a local
35 * Create a new full repo workspace [using a fresh local mirror](https://source.android.com/setup/bu…
39 * Remove a full repo workspace with no build artifacts
101 to a location in your path. For example:
108 ## How do I make sure that creating a hacksaw workspace is fast?
110 Hacksaw creates bind mounts for all git projects in a codebase. It then
111 copies **everything** else. Make sure you remove all build artifacts from a
112 codebase before create a workspace, otherwise it may spend a long time copying
130 Hacksawd is a privileged system daemon whose only job is to manage bind mounts.
140 The installation scripts creates a new "hacksaw" group and adds you to it. You
158 a workspace to a codebase. When you mark a project for editing then
159 its read-only bind mount gets replaced by a writable Git worktree.
169 * Failing to create a workspace is not rolled back.
170 * Editing nested projects is not supported yet. So if you have a git project
174 * Syncing a codebase does update the existing projects in all attached
176   should be a new "workspace sync" command for that?