#17 open
ernest.prabhakar (at gmail)

Support git repository format

Reported by ernest.prabhakar (at gmail) | December 7th, 2009 @ 09:59 PM | in Basic git workflow

Since nobody else seems to have filed it, this bug is to request that AMP be able to read and write from the GIT repository format.

The key functionality for doing so appears to be:

Reading - http://www.kernel.org/pub/software/scm/git/docs/git-read-tree.html

Writing - http://www.kernel.org/pub/software/scm/git/docs/git-update-index.html

according to:

http://www.kernel.org/pub/software/scm/git/docs/
Low-level commands (plumbing)

Although git includes its own porcelain layer, its low-level commands are sufficient to support development of alternative porcelains. Developers of such porcelains might start by reading about git-update-index(1) and git-read-tree(1).

The interface (input, output, set of options and the semantics) to these low-level commands are meant to be a lot more stable than Porcelain level commands, because these commands are primarily for scripted use. The interface to Porcelain commands on the other hand are subject to change in order to improve the end user experience.

The following description divides the low-level commands into commands that manipulate objects (in the repository, index, and working tree), commands that interrogate and compare objects, and commands that move objects and references between repositories.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Rethink Version Control.- http://amp.carboni.ca/

Amp aims to put control of version-control software in your hands as a developer. The entire system is written in Ruby (with C extensions to improve performance), and aims to implement all major VCS's in Ruby. Currently, Mercurial is implemented.

Other features:
Commands are first-class members of the system - drop in an "Ampfile" in your repository, and you can add commands to amp in the same manner you add commands to rake (only with far, far more power!)
Documentation is one of our biggest priorities. We require all methods to be documented - even comically simple ones.
Heavy testing.
Multiple "workflows" - use git's commands to power a mercurial repository.
Add hooks/callbacks in minutes.

Shared Ticket Bins

People watching this ticket

Tags

Pages