For one reason or another, I thought it would be useful to have a look at the
Csound source code. So I've tried setting up git, in order to download it.
I'm having no luck.

I would rather not ask anyone on the Csound list to spend hours walking me
through the process step by step. Instead, I'd like to ask a question that
might (I hope) have a simple answer:

How the heck would I learn to do this WITHOUT asking anyone to spend hours
walking me through the process? Is there a way to do that?

I'm reading the Git manual -- or rather, an online book of some sort with
what seems to be an official imprimatur. It's clearly written, anyway. I
seem to have downloaded the MacOS 10.6 version and installed it (though the
book tells me it's in /usr/bin/, and there ain't no such directory, or at
least none that is visible from Finder). It seems to be running fine from
the Terminal.

But when I try to clone the Csound repository using the command:

git clone git://csound.git.sourceforge.net/gitroot/csound/csound

...I get the response, "Warning: You appear to have cloned an empty
repository." This is the point at which I throw up my hands and say, "I have
no idea what I'm messing with here." And of course, the book isn't going to
tell me what's wrong. The book is written (not surprisingly) in a way that
assumes everything will go smoothly, and if it doesn't, the reader will know
how to work it through, because the reader is a seasoned professional with
advanced degrees in computer science.

So I return to my basic question: How would I go about learning this stuff,
preferably without pestering busy people with dozens of basic questions?
Thanks in advance for any guidance!

--Jim Aikin





--
View this message in context: http://csound.1045644.n5.nabble.com/Semi-Off-Topic-Git-tp5715754.html
Sent from the Csound - General mailing list archive at Nabble.com.

Macs hide /usr/bin from the GUI because if someone moves things or
renames things there (or /bin /sbin /lib /usr/lib /efi etc.) they can
make their machine unusable.


On Thu, Sep 13, 2012 at 7:32 PM, Jim Aikin  wrote:
> For one reason or another, I thought it would be useful to have a look at the
> Csound source code. So I've tried setting up git, in order to download it.
> I'm having no luck.
>
> I would rather not ask anyone on the Csound list to spend hours walking me
> through the process step by step. Instead, I'd like to ask a question that
> might (I hope) have a simple answer:
>
> How the heck would I learn to do this WITHOUT asking anyone to spend hours
> walking me through the process? Is there a way to do that?
>
> I'm reading the Git manual -- or rather, an online book of some sort with
> what seems to be an official imprimatur. It's clearly written, anyway. I
> seem to have downloaded the MacOS 10.6 version and installed it (though the
> book tells me it's in /usr/bin/, and there ain't no such directory, or at
> least none that is visible from Finder). It seems to be running fine from
> the Terminal.
>
> But when I try to clone the Csound repository using the command:
>
> git clone git://csound.git.sourceforge.net/gitroot/csound/csound
>
> ...I get the response, "Warning: You appear to have cloned an empty
> repository." This is the point at which I throw up my hands and say, "I have
> no idea what I'm messing with here." And of course, the book isn't going to
> tell me what's wrong. The book is written (not surprisingly) in a way that
> assumes everything will go smoothly, and if it doesn't, the reader will know
> how to work it through, because the reader is a seasoned professional with
> advanced degrees in computer science.
>
> So I return to my basic question: How would I go about learning this stuff,
> preferably without pestering busy people with dozens of basic questions?
> Thanks in advance for any guidance!
>
> --Jim Aikin
>
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Semi-Off-Topic-Git-tp5715754.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

to actually address your main issue:

the instructions on
http://sourceforge.net/scm/?type=git&group_id=81968 are incorrect

you should clone git://csound.git.sourceforge.net/gitroot/csound/csound5
(note the 5 at the end)

On Thu, Sep 13, 2012 at 8:20 PM, Justin Smith  wrote:
> Macs hide /usr/bin from the GUI because if someone moves things or
> renames things there (or /bin /sbin /lib /usr/lib /efi etc.) they can
> make their machine unusable.
>
>
> On Thu, Sep 13, 2012 at 7:32 PM, Jim Aikin  wrote:
>> For one reason or another, I thought it would be useful to have a look at the
>> Csound source code. So I've tried setting up git, in order to download it.
>> I'm having no luck.
>>
>> I would rather not ask anyone on the Csound list to spend hours walking me
>> through the process step by step. Instead, I'd like to ask a question that
>> might (I hope) have a simple answer:
>>
>> How the heck would I learn to do this WITHOUT asking anyone to spend hours
>> walking me through the process? Is there a way to do that?
>>
>> I'm reading the Git manual -- or rather, an online book of some sort with
>> what seems to be an official imprimatur. It's clearly written, anyway. I
>> seem to have downloaded the MacOS 10.6 version and installed it (though the
>> book tells me it's in /usr/bin/, and there ain't no such directory, or at
>> least none that is visible from Finder). It seems to be running fine from
>> the Terminal.
>>
>> But when I try to clone the Csound repository using the command:
>>
>> git clone git://csound.git.sourceforge.net/gitroot/csound/csound
>>
>> ...I get the response, "Warning: You appear to have cloned an empty
>> repository." This is the point at which I throw up my hands and say, "I have
>> no idea what I'm messing with here." And of course, the book isn't going to
>> tell me what's wrong. The book is written (not surprisingly) in a way that
>> assumes everything will go smoothly, and if it doesn't, the reader will know
>> how to work it through, because the reader is a seasoned professional with
>> advanced degrees in computer science.
>>
>> So I return to my basic question: How would I go about learning this stuff,
>> preferably without pestering busy people with dozens of basic questions?
>> Thanks in advance for any guidance!
>>
>> --Jim Aikin
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://csound.1045644.n5.nabble.com/Semi-Off-Topic-Git-tp5715754.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>

BTW, git is at /usr/local/git/bin/git on my OS X machine.

Phil Thomson
http://philthomson.ca/

On 12-09-13 8:34 PM, Justin Smith wrote:
> to actually address your main issue:
>
> the instructions on
> http://sourceforge.net/scm/?type=git&group_id=81968 are incorrect
>
> you should clone git://csound.git.sourceforge.net/gitroot/csound/csound5
> (note the 5 at the end)
>
> On Thu, Sep 13, 2012 at 8:20 PM, Justin Smith  wrote:
>> Macs hide /usr/bin from the GUI because if someone moves things or
>> renames things there (or /bin /sbin /lib /usr/lib /efi etc.) they can
>> make their machine unusable.
>>
>>
>> On Thu, Sep 13, 2012 at 7:32 PM, Jim Aikin  wrote:
>>> For one reason or another, I thought it would be useful to have a look at the
>>> Csound source code. So I've tried setting up git, in order to download it.
>>> I'm having no luck.
>>>
>>> I would rather not ask anyone on the Csound list to spend hours walking me
>>> through the process step by step. Instead, I'd like to ask a question that
>>> might (I hope) have a simple answer:
>>>
>>> How the heck would I learn to do this WITHOUT asking anyone to spend hours
>>> walking me through the process? Is there a way to do that?
>>>
>>> I'm reading the Git manual -- or rather, an online book of some sort with
>>> what seems to be an official imprimatur. It's clearly written, anyway. I
>>> seem to have downloaded the MacOS 10.6 version and installed it (though the
>>> book tells me it's in /usr/bin/, and there ain't no such directory, or at
>>> least none that is visible from Finder). It seems to be running fine from
>>> the Terminal.
>>>
>>> But when I try to clone the Csound repository using the command:
>>>
>>> git clone git://csound.git.sourceforge.net/gitroot/csound/csound
>>>
>>> ...I get the response, "Warning: You appear to have cloned an empty
>>> repository." This is the point at which I throw up my hands and say, "I have
>>> no idea what I'm messing with here." And of course, the book isn't going to
>>> tell me what's wrong. The book is written (not surprisingly) in a way that
>>> assumes everything will go smoothly, and if it doesn't, the reader will know
>>> how to work it through, because the reader is a seasoned professional with
>>> advanced degrees in computer science.
>>>
>>> So I return to my basic question: How would I go about learning this stuff,
>>> preferably without pestering busy people with dozens of basic questions?
>>> Thanks in advance for any guidance!
>>>
>>> --Jim Aikin
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context: http://csound.1045644.n5.nabble.com/Semi-Off-Topic-Git-tp5715754.html
>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>              https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

> the instructions on
> http://sourceforge.net/scm/?type=git&group_id=81968 are incorrect

Ah. That would make a difference, wouldn't it? It's downloading now. Thanks!

What I'll do with it now that I have a local copy, God only knows. But
progress is being made, bit by bit.




--
View this message in context: http://csound.1045644.n5.nabble.com/Semi-Off-Topic-Git-tp5715754p5715759.html
Sent from the Csound - General mailing list archive at Nabble.com.

I got that same error and actually worked around it by using the web
interface to find the appropriate tree. Still the instructions need to
be fixed if at all possible.

On 9/14/12, Jim Aikin  wrote:
>> the instructions on
>> http://sourceforge.net/scm/?type=git&group_id=81968 are incorrect
>
> Ah. That would make a difference, wouldn't it? It's downloading now.
> Thanks!
>
> What I'll do with it now that I have a local copy, God only knows. But
> progress is being made, bit by bit.
>
>
>
>
> --
> View this message in context:
> http://csound.1045644.n5.nabble.com/Semi-Off-Topic-Git-tp5715754p5715759.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>

On Thu, Sep 13, 2012 at 9:32 PM, Jim Aikin  wrote:
> So I return to my basic question: How would I go about learning this stuff,
> preferably without pestering busy people with dozens of basic questions?
> Thanks in advance for any guidance!
>
> --Jim Aikin

Jim,

   I've found that a Google search with the error message as search
text often helps. Sometimes it will give you a complete answer, other
times it will at least suggest some additional things to check.

David Bowen