Re: [GSoC] What is status of Git's Google Summer of Code 2008 projects?

From: Miklos Vajna <vmiklos@frugalware.org>
Date: Jul 9, 2008, 10:56 UTC
Message-ID: <20080709105623.GP10347@genesis.frugalware.org>
In-Reply-To: <bd6139dc0807090318r4cbcac93s907871c6b45c03ac@mail.gmail.com>

On Wed, Jul 09, 2008 at 12:18:41PM +0200, Sverre Rabbelier <alturin@gmail.com> wrote:

> I am not yet sure how I should send in my code for peer review.
> $ git rev-list master | wc -l
> 151

What I did squashing fixes regularly, but I keep a 'history' branch where I always reference to the old HEAD, so others can still have a look at the individual commits.

It's like:

$ cat rebase-builtin-merge.sh #!/bin/sh -e

[ -n "$*" ]

old_head=$(git rev-parse HEAD)
git rebase $*
git update-ref refs/heads/rebase-history \
        $(echo "Rebased with 'git rebase $*'" | \
        git commit-tree HEAD^{tree} -p rebase-history -p $old_head -p HEAD)

It will not work properly if you get conflicts, but you got the idea.