| commit | 06a9870536e55319082fa86cc4ac36d5e0b5fb20 | [log] [download] |
|---|---|---|
| author | Gustaf Lundh <gustaf.lundh@sonymobile.com> | Mon Aug 17 17:29:11 2015 +0200 |
| committer | Gustaf Lundh <gustaf.lundh@sonymobile.com> | Mon Aug 17 17:46:03 2015 +0000 |
| tree | 7d318ffd7bc1ff189c09366c28ed1cf955ac9af8 | |
| parent | 70d8454361ac075e86d5e9a2612e42e76128fb66 [diff] |
Minimize reading of all refs from disk When displaying the commit log, all refs was fetch from the repository for each of the 20 most recent commits displayed. By not destroying the Builder objects unneccesarily often we can cache the refs and reuse them for each commit. On heavy gits with a lot of refs, we could fetch the page 20 times faster than before. Change-Id: Ief060002b295abfe0ca01d194504c95502891e39
Gitiles is a simple repository browser for Git repositories, built on JGit. Its guiding principle is simplicity: it has no formal access controls, no write access, no fancy Javascript, etc.
Gitiles requires Buck to build.
sudo apt-get install ant
cd ${HOME}
git clone https://github.com/facebook/buck.git
cd buck
ant
sudo ln -s ${PWD}/bin/buck /usr/bin/buck
cd /path/to/gitiles
git submodule update --init
buck build all
cd /path/to/repositories # Don't run from the gitiles repo. /path/to/gitiles/tools/run_dev.sh
This will recompile and start a development server. Open http://localhost:8080/ to view your local copy of gitiles, which will serve any repositories under /path/to/repositories.
If you'd like to use Eclipse to edit Gitiles, first generate a project file:
./bucklets/tools/eclipse.py --src
Import the project in Eclipse:
File -> Import -> Existing Projects into Workpace
The project only needs to be rebuilt if the source roots or third-party libraries have changed. For best results, ensure the project is closed in Eclipse before rebuilding.
Gitiles uses Gerrit for code review: https://gerrit-review.googlesource.com/
Gitiles uses the “git push” workflow with server https://gerrit.googlesource.com/gitiles. You will need a generated cookie.
Gerrit depends on “Change-Id” annotations in your commit message. If you try to push a commit without one, it will explain how to install the proper git-hook:
curl -Lo `git rev-parse --git-dir`/hooks/commit-msg \
https://gerrit-review.googlesource.com/tools/hooks/commit-msg
chmod +x `git rev-parse --git-dir`/hooks/commit-msg
Before you create your local commit (which you'll push to Gerrit) you will need to set your email to match your Gerrit account:
git config --local --add user.email foo@bar.com
Normally you will create code reviews by pushing for master:
git push origin HEAD:refs/for/master