oop, I have some git command aliases defined. change git co -> git checkout =Dennis Heimbigner Unidata On 9/2/2016 12:51 PM, Dave Allured - NOAA Affiliate wrote: > New Client Reply: Authorize github access > > [PRIVATE] > Dennis, > > Thanks for the advice on github. Everything works fine until step 6. I am > using git version 2.6.2 on OSX 10.11.6: > > mac56:~/git/netcdf-c 15> git co issue314.allured > git: 'co' is not a git command. See 'git --help'. > > Did you mean one of these? > commit > clone > log > > Your advice? > > --Dave > > > address@hidden> wrote: > >> Ok, lets get you started. >> 1. pick a directory into which you want to place the netcdf-c fork. >> I typically use a directory called 'git' (name is only a mnemonic). >> mkdir git >> 2. move to the git directory: >> cd git >> 3. The fork is created by executing this command in the 'git' (or whatever) >> directory >> git clone https://github.com/Unidata/netcdf-c.git >> [Note if you look at the netcdf-c home page on github >> (https://github.com/Unidata/netcdf-c), you should see >> a "clone or download" drop-down in the upper right. >> It will show the url to use with 'git clone'.] >> 4. Move into the netcdf-c directory >> cd netcdf-c >> 5. create a new branch for your changes: >> git branch newbranchname >> 6. move to the new branch >> git co newbranchname. >> >> This should get you started. >> >> =Dennis Heimbigner >> Unidata >> >> Ticket Details >> =================== >> Ticket ID: DZC-590249 >> Department: Support netCDF >> Priority: Normal >> Status: Open >> =================== >> > > > > Ticket Details > =================== > Ticket ID: DZC-590249 > Department: Support netCDF > Priority: Normal > Status: Open > Link: > https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=27459 > Ticket Details =================== Ticket ID: DZC-590249 Department: Support netCDF Priority: Normal Status: Open =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.