[PATCH] Add a source_tree field to Project.

[Guilherme Salgado]

On Wed, 2011-03-30 at 12:10 +0800, Jeremy Kerr wrote:
> Hi Guilherme,
> 
> >  apps/patchwork/models.py                      |    1 +
> >  lib/sql/migration/008-project-source-tree.sql |    3 +++
> >  2 files changed, 4 insertions(+), 0 deletions(-)
> >  create mode 100644 lib/sql/migration/008-project-source-tree.sql
> 
> Looks good. I'd like to wait until there is a user of this field before 
> merging the change though - or are you using this for linaro-internal things?

I'm using it on a script I'm writing to fetch the git history of every
project and scan that looking for patches that have been committed. Just
like the existing patchwork-update-commits script does but this one is
fully automated, and to make it more easily testable I'm experimenting
with python-dulwich to scan the git history. 

I haven't submitted it for feedback yet because it's still very much a
work in progress, but I would certainly do so. (I'm including what I
have so far here, though)

Oh, there's one extra DB schema change I'm considering... That will
allow us to keep track of the last seen commit ref so that we can scan
the git history incrementally.  I've added it as another field to
Project, named last_seen_commit_ref.  How does that sound to you?


-- 
Guilherme Salgado <https://launchpad.net/~salgado>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-commit-detection.diff
Type: text/x-patch
Size: 9064 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20110330/6083957c/attachment-0001.bin>
-------------- 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/20110330/6083957c/attachment-0001.pgp>