Agreed. But we should make sure that we keep the old packages. Just to be sure.


On 07.11.2012, at 09:46, Camillo Bruni <camillobr...@gmail.com> wrote:

> 
> On 2012-11-07, at 09:45, Max Leske <maxle...@gmail.com> wrote:
> 
>> There is also no support for working copies (i.e. we track changes in the 
>> image at the moment but command-line Git won't know about it).
>> 
>> That's the wrong repo Camillo :)
> 
> dammit! :D we should delete the old ones then, it's such a mess I never know 
> where to look..
> 
>> Use the Filesystem-Git repository I pointed you to.
>> 
>> Max
>> 
>> On 07.11.2012, at 09:36, Camillo Bruni <camillobr...@gmail.com> wrote:
>> 
>>> We have a almost 100% working git library for the low-level api.
>>> We have the git:// and dumb http:// protocol almost fully defined, we still 
>>> miss
>>> smart http://.
>>> 
>>> The only thing we cannot do yet properly is cloning a repository, but
>>> that can be easily scripted with OSProcess.
>>> 
>>> The latest sources with plenty of tests are available here:
>>> http://ss3.gemstone.com/ss/FSGit-Experimental.html
>>> 
>>> 
>>> On 2012-11-07, at 09:08, "roberto.mine...@usi.ch" <roberto.mine...@usi.ch> 
>>> wrote:
>>> 
>>>> Hello,
>>>> 
>>>> I need to access a Git repository programmatically from Pharo.
>>>> 
>>>> Is there any API to work with Git working copies, access and manipulate 
>>>> repositories programmatically?
>>>> 
>>>> In short I need to checkout each revision of a project and extract some 
>>>> meta-data from each revision. 
>>>> 
>>>> Thanks in advance,
>>>> Roberto
>>> 
>>> 
>> 
>> 
> 
> 


Reply via email to