On 23/05/2011 15:52, Daniel Peebles wrote:
Aren't the fingerprints effectively the same as what git submodules
already do? If we're going to start recording fingerprints, why not just
move to using submodules for the dependent repositories?

Yes, they are what git submodules do. However, submodules add a considerable amount of complexity to our workflows, and when I tried it the implementation of submodules was sufficiently flaky and confusing that I was put off, at least for the time being.

Cheers,
        Simon



On Mon, May 23, 2011 at 10:39 AM, David Peixotto <[email protected]
<mailto:[email protected]>> wrote:


    On May 22, 2011, at 9:16 PM, Erik de Castro Lopo wrote:

     > Interesting tool. Do you have a set of these fingerprints dating back
     > a year or more?

    No, unfortunately I just wrote the script after the discussion in
    this thread. I see it as a way to help in the future, but I don't
    think it will help with your current problem.

    Of course for it to be useful in the future we need to actually
    record the fingerprints somewhere. It seems we could either add
    Simons sync-all log command output to the builder output, or we
    could generate separate fingerprint files from a post-commit hook or
    a cron job. Having separate files is a bit cleaner, but perhaps more
    hassle.

     > Over the weekend I hacked together a tool (in Haskell) that can parse
     > the git logs of the various repositories and for a given date, put
     > together a bunch of git commit hashes (one for each repo) that should
     > work together.

    This sounds useful. If you wanted to generate your hashes in the
    fingerprint format (e.g. repo|hash) then the tools could be used
    together quite well.



    _______________________________________________
    Cvs-ghc mailing list
    [email protected] <mailto:[email protected]>
    http://www.haskell.org/mailman/listinfo/cvs-ghc




_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc


_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to