On Fri, Apr 28, 2017 at 01:05:47AM +0800, Ben Coman wrote: > The natural thing for us in pharo-land is to script to movement of MC HTTP > repos to git. > This article describes why it actually could be worthwhile ensuring moving > git to MC HTTP is also easy...
Technically speaking moving between GitFileTree and MC should be bi-directional, at least in the old script there was nothing requiring the endpoint be git (it is just deep copy of commits between two MC repos). Now I am updating the script, and I don't know if it will be preserved, but I'll keep it in mind. Peter > > https://www.joelonsoftware.com/2000/06/03/strategy-letter-iii-let-me-go-back/ > > cheers -ben > > On Fri, Apr 28, 2017 at 12:35 AM, Thierry Goubier <[email protected] > > wrote: > > > Hi Eliot, > > > > this is not possible in a FileTree repository, since it requires > > manipulating the underlying vcs, which may be anything. > > > > If it is a git-based repository used with filetree, then there are other > > solutions: gitfiletree and iceberg will show you the list of versions and > > allow you to access all of them. A Gofer script may then be used to export > > the versions one by one to any repository, if you really require that. > > > > Regards, > > > > Thierry > > > > > > Le 27/04/2017 à 18:24, Eliot Miranda a écrit : > > > >> Hi All, > >> > >> anyone have a script for copying versions of packages in filetree > >> repositories into MC HTTP repositories? > >> > >> I'm looking at a filetree: repository for a package right now and... > >> - in the repository browser only Foo.package appears, not a list of > >> versions > >> - when I view the history of the package I get a list of versions but > >> there is no menu on selections from the list, so no obvious way of > >> accessing a version (browsing it, copying it, viewing differences > >> between versions, etc) > >> > >> _,,,^..^,,,_ > >> best, Eliot > >> > > > > > >
