[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Monotone-viz and repository structure.
From: |
Stephen Leake |
Subject: |
Re: [Monotone-devel] Monotone-viz and repository structure. |
Date: |
Tue, 23 Feb 2010 03:48:41 -0500 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.2 (windows-nt) |
address@hidden writes:
> On Mon, Feb 22, 2010 at 11:06:13AM +0100, Thomas Moschny wrote:
>> Hi Hendrik,
>>
>> Am Sun, 21 Feb 2010 15:57:57 -0500
>> schrieb address@hidden:
>>
>> > On Sun, Feb 21, 2010 at 03:35:42PM -0500, address@hidden
>> > wrote:
>> > > I have my own copy of the monotone repository. At least I think I
>> > > do. It seems to sync properly when I pull.
>> > >
>> > > But I' trying to obtain monotone-viz. It doesn't seem to be in my
>> > > repository, Is this just an accident of history, that I failed to
>> > > specify the branch when I pulled monotone initially? Or is it,
>> > > and should it be, in a completely separate repository?
>>
>> It is in the branch "net.venge.monotone-viz" (and some subbranches
>> thereof) in the monotone repository served at monotone.ca. Depending on
>> the pattern you are using (see "mtn ls vars database") this branch name
>> might have never matched during pull for you.
>
> Thanks. I was more-or-less asking about best practices rather than
> trying to solve a problem.
>
> If it is in the same repository at "headquarters", it makes some to be
> consistent and put it in the same repository here. But I am starting
> to suspect that it really doesn't matter much.
Right; you can pull any branch into any repository (= monotone
database). But then you do have to be careful not to accidentally send
a branch to an upstream repository; we don't want to have non-monotone
branches in the database at monotone.ca.
--
-- Stephe