box "off" fails

Jaroslav Hajek highegg at gmail.com
Fri Aug 1 01:57:18 CDT 2008


On Thu, Jul 31, 2008 at 9:13 PM, John W. Eaton <jwe at bevo.che.wisc.edu> wrote:
> On 31-Jul-2008, Jaroslav Hajek wrote:
>
> | OK, I transplanted this into the release-3-0-x repo
> | <http://hg.tw-math.de/release-3-0-x/>
>
> OK, now that this is available, I will keep a local copy of this
> archive on my system now, and strip the release-3-0-x branch from the
> main development archive that I use.
>
> | I'll start managing release-3-2-x as soon as John tags a suitable
> | initial revision in the main archive (which was his suggestion).
>
> OK.  I assume the release-3-2-x branch will just start as a clone of
> the main development archive at the point when there is a 3.2.0
> release, or perhaps we would decide to create the release branch
> slightly before the actual release, then just merge changes for the
> release in that archive, possibly also copying them to other branches
> as well (main, release-3-0-x, wherever appropriate).
>
> | btw, I did this by first updating my repo (highegg) and then using "hg
> | transplant" to get the changeset into release-3-0-x. Since I intend to
> | use the highegg repo for other stuff, it seems I could use a "pristine
> | clone" repo. (I could, of course, transplant directly from web, but
> | working with local repo is more convenient). I think that Michael and
> | Shai also used a local clone of John's main repo for the graphics
> | development. Perhaps there could be one for everyone?
>
> I'm not sure I understand what you mean by "one for everyone".
>
> | We would all need to be able to do "hg pull" in the repo, however.
>
> I don't follow this either.  Can you explain in more detail what sort
> of layout of archives you are proposing?  The way I look at it,
> archives on the web are usually just there for public access.  For
> example, I don't actually work directly with the one that I make
> publicly available.  Instead, I work on some collection of archives on
> my local system, then push changes to the public archive when they are
> ready for others to see.  So the public archive is push only for me
> and pull/clone only for others.  Are you proposing some other way of
> working with the public archives like the one you now have for the
> release-3-0-x branch?

Um, sorry - don't mind that, the suggestion was actually dedicated to
Thomas. I suggested that he kept a pure clone of your main repo
amongst the other repos, so that people can update their repos from a
local common source (to save space on the server). But now I see that
it only makes sense when working directly on the remote server, which
is not what one will typically do (though I did it yesterday). So
forget about this.


>
> Thanks,
>
> jwe
>



-- 
RNDr. Jaroslav Hajek
computing expert
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz


More information about the Bug-octave mailing list