Fully automating patch state updates

[Guilherme Salgado]

On Fri, 2011-03-25 at 16:02 +0800, Jeremy Kerr wrote:
> Hi Guilherme,
> 
> > I've seen the tools/patchwork-update-commits script and I'm planning to
> > work on making a fully automated version of it, which fetches the master
> > branch, scans the commits on it and updates the state of patches. I think
> > this would be a nice addition to Patchwork.
> > 
> > For that to work, though, the first thing we need is to know where's the
> > master branch of a project.  The patch below makes that possible by adding
> > a free form char field to store the URL to the project's master branch.
> > It's not a URLField because that only allows http[s] URLs, which is not
> > what we want.
> 
> OK, this makes sense. I'd suggest calling this "source_tree" instead, with the 
> intention of using any VCS URL there; "branch" means different things to 
> different VCSes.

Fair enough, I've renamed it and submitted again, this time signed as
well.

Cheers,

-- 
Guilherme Salgado <https://launchpad.net/~salgado>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20110325/cb491084/attachment.pgp>