Le 10/07/2014 18:59, Damien Pollet a écrit :
as far as I am concerned (I'm certainly not up-to-date on recent enhancements)…
- filetree is a pain because of the double-commit workflow (MC with
dummy message to serialize, then git)
- gitfiletree is a pain because it insists on using a file
Sorry to hijack this discussion… is it by design that the github:
scheme takes a snapshot instead of a git clone?
github: is convenient for the metacello syntax, but since it just
takes a snapshot of a commit, there is no immediate way of pushing
changes back. Converting what's on disk to a
as far as I am concerned (I'm certainly not up-to-date on recent enhancements)…
- filetree is a pain because of the double-commit workflow (MC with
dummy message to serialize, then git)
- gitfiletree is a pain because it insists on using a file browser
that shows all dotfiles and starts in the
Damien,
Yes it was by design to just snapshot ...
At the time, git was not necessarily familiar to most smalltalkers and I
didn't want to require that git be installed or that a user understand how
to use git, just to download and _use_ the code of a project that was
hosted on github. A clone
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Damien Pollet
[damien.pol...@gmail.com]
Envoyé : jeudi 10 juillet 2014 18:59
À : Pharo Development List
Objet : Re: [Pharo-dev] Metacello-github + filetree-git async
as far as I am
Le 06/03/2014 09:32, Yuriy Tymchuk a écrit :
Hi guys.
My workflow is like this:
I load a configuration on CI with github:// magic in metacello conf.
Then on local machine I add a local gitfiletree repo to the project packages.
The thing is that the last version if loaded, but gitfiletree
On 06 Mar 2014, at 09:48, Goubier Thierry thierry.goub...@cea.fr wrote:
Le 06/03/2014 09:32, Yuriy Tymchuk a écrit :
Hi guys.
My workflow is like this:
I load a configuration on CI with github:// magic in metacello conf.
Then on local machine I add a local gitfiletree repo to the
Le 06/03/2014 10:08, Yuriy Tymchuk a écrit :
On 06 Mar 2014, at 09:48, Goubier Thierry thierry.goub...@cea.fr wrote:
Le 06/03/2014 09:32, Yuriy Tymchuk a écrit :
Hi guys.
My workflow is like this:
I load a configuration on CI with github:// magic in metacello conf.
Then on local
On 06 Mar 2014, at 11:17, Goubier Thierry thierry.goub...@cea.fr wrote:
Le 06/03/2014 11:09, Yuriy Tymchuk a écrit :
Sent from my iPhone
On 06 Mar 2014, at 10:28, Goubier Thierry thierry.goub...@cea.fr wrote:
Le 06/03/2014 10:08, Yuriy Tymchuk a écrit :
On 06 Mar 2014, at
On 06 Mar 2014, at 11:35, Yuriy Tymchuk yuriy.tymc...@me.com wrote:
On 06 Mar 2014, at 11:17, Goubier Thierry thierry.goub...@cea.fr wrote:
Le 06/03/2014 11:09, Yuriy Tymchuk a écrit :
Sent from my iPhone
On 06 Mar 2014, at 10:28, Goubier Thierry thierry.goub...@cea.fr wrote:
Ok, I see now.
I don't think this can be avoided; it's inherent in the way both github:
and gitfiletree: understand repositories. The explanation will go a bit
into git and gitfiletree design and FileTree; in the mean time, you may
either change a bit the config to clean that (force a load of
11 matches
Mail list logo
