James Falkner wrote:
Trevor Watson wrote:I don't think that this goes nearly as far as you wanted James, but I have a server set up to host (and archive) webrevs for our organisation.With apologies for the internal linky: http://bamia-web.israel:81/WebRev/listThis takes a compressed tarball of the webrev output and puts it into a project based structure.I was going to try to wrestle with 'wget' to enable the webrev to be POST'ed automatically when 'make webrev' was run in the repo, but just didn't get around to it. That and the 1001 other enhancements it needs ;)Cool, thanks. Indexing by bug # sounds like the right thing to do. The other idea floating around was to use the repository itself as a repository of webrevs. So the webrev would be 'hg push'ed. Only concern I had was that everyone would be constantly merging with the changesets introduced. Thoughts anyone?
My first reaction to that was ewwwww!I can see what you want to achieve, but I don't see a repo as the way to go since each webrev will be physically independent of its predecessors and successors, even if they are logically connected.
What I guess I'm trying to say is that a webrev will not change once posted, so why use something as complex as an SCM to contain it when a relatively simple directory hierarchy could do the job.
My 2ยข anyway. Trev
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
