Re: Cogito Tutorial If It Helps

On Tuesday 26 April 2005 21:52, James Purser wrote:
> I reworked the previous tutorial to take in the changes in the scripts.
> Will make this a series of tutorials to cover all aspects. Any
> suggestions or hints or spelling corrections would be most welcome.
>
> http://ksit.dynalias.com/articles.php?s_id=46&art_id=41

Although I have been reading this mailing list since almost the beginning, I 
have not had a chance to download and try anything.  Using this message as an 
incentive to start, I started to follow this.

However I have run into problems.  

Let me try and explain.

The first part of the tutorial of loading the tarball and building things is 
fine (should be, its a well trodden mental model) - and actually for me I did 
not have libcurl3-dev installed the first time - but because I already had 
the mental model in my mind on this stage it was easy to fit.

I then issued the cg-clone command to get a fresh copy of cogito.  This is 
where I think it would be useful to take time-out from the tutorial and 
explain what I have here.  For me at least, if I don't have a mental model of 
what is happening, I am totally confused.

I "think" I understand the git repository with the various content addressable 
objects.  Reading the README file describes that quite well.  I assume that 
is what is stored in the .git subdirectory (although I have yet to find any 
text that formally says that).

Where I am confused is the relationship between what is in the .git 
subdirectory and the project tree of cogito that sits around it.  Obviously I 
understand that its the latest version of the project as represented by the 
objects in the repository, but what I don't really understand (and neither 
your tutorial nor all the explanations of each of the commands in the README 
really explain it either) is how the various commands adjust the 
relationship.

For instance cg-branch-add seems to add a branch to the repository from a url 
(I assume it downloads any "blobs" etc that are not already in my local 
repository and creates a tag that identifies the head of a tree object), but 
a don't understand how I am supposed see that particular branch as expanded 
code.  (I suspect it might be cg-seek, but I am not really sure - and if it 
is how do you find out what branch this expanded code is now pointed to?).  
But what do cg-update and cg-pull do in terms of the uncompressed code 
sitting in the surrounding directory round the repository, particularly when 
you perform them on a branch that is not the one that the code refers to.  


The reason I raise all this, is when I follow through on your tutorial and get 
to the cg-diff stage I get this

xargs: cg-Xdiffdo: No such file or directory

And I have absolutely no idea whats wrong or where to start looking.



-- 
Alan Chandler
http://www.chandlerfamily.org.uk
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html