From: Seth Falcon <seth@userprimary.net>
Date: Sat, 17 May 2008 21:30:39 GMT
Subject: Re: git and peer review
Message-ID: <20080517213039.GR396@ziti.local>
In-Reply-To: <87k5i9u8f1.fsf@nav-akl-pcn-343.mitacad.com>

* On 2008-05-05 at 08:21 +1200 Toby Allsopp wrote:
> I do something similar using git filter-branch --msg-filter.  I have a
> little shell script call git-add-checked (our convention is to have a
> "checked: " line in the commit message):

That's a useful script, thanks for posting it.  I'd like to make it a
bit safer to use -- the first time I tried it I didn't give any branch
limiting args and it started filtering a lot of history :-P

What I would like is a way for the script to determine the appropriate
tracking branch.  So that the usage would look like:

   git mark-reviewed someone@userprimary.net

and it would figure out whether it should do trunk.. or release-1.3..,
etc.  Can anyone point me in the right direction?


-- 
Seth Falcon | http://userprimary.net/user/