On Thu, Sep 02, 2010 at 07:07:07PM +0100, Luke Kenneth Casson Leighton wrote:
> On Thu, Sep 2, 2010 at 4:58 PM, Jeff King <peff@xxxxxxxx> wrote:
> i think.... i think i miiight be able, hmmm... i believe it would be
> possible to implement this last option by creating separate .torrents
> for packs (one each!). by splitting things down, so that pack objects
> are named as {ref}-{objref}-{SHA-1}.torrent and by providing a "top
> level" torrent which contains the refs/heads/* and the associate
> rev-list(s)... each set of rev-lists would have the SHA-1 of the
> pack-object that happened to be created (and shared) at that
> particular time, from that particular client: you then genuinely don't
> give a stuff about who has what, it's all the same, and...
>
You seem to have some misconceptions about refs too. refs are absolutely
not common between two machines. The branch "master" on my box might
match the branch "linux-2.6" on git.kernel.org. And it might be from two
days ago.
A ref is just an annotation in /one particular repository/ that a
particular commit is interesting to it for some reason.
--CJD
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html