thanks for YOUR assistance....obviously I am not a git-spurt......and I am taking your commands literally...no go for me. Same with sudo prefix.
pi@Sprinklers:~ $ git checkout master
fatal: Not a git repository (or any of the parent directories): .git
pi@Sprinklers:~ $ git
usage: git [--version] [--help] [-C <path>] [-c name=value]
[--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
[-p | --paginate | --no-pager] [--no-replace-objects] [--bare]
[--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
<command> [<args>]
These are common Git commands used in various situations:
start a working area (see also: git help tutorial)
clone Clone a repository into a new directory
init Create an empty Git repository or reinitialize an existing one
work on the current change (see also: git help everyday)
add Add file contents to the index
mv Move or rename a file, a directory, or a symlink
reset Reset current HEAD to the specified state
rm Remove files from the working tree and from the index
examine the history and state (see also: git help revisions)
bisect Use binary search to find the commit that introduced a bug
grep Print lines matching a pattern
log Show commit logs
show Show various types of objects
status Show the working tree status
grow, mark and tweak your common history
branch List, create, or delete branches
checkout Switch branches or restore working tree files
commit Record changes to the repository
diff Show changes between commits, commit and working tree, etc
merge Join two or more development histories together
rebase Reapply commits on top of another base tip
tag Create, list, delete or verify a tag object signed with GPG
collaborate (see also: git help workflows)
fetch Download objects and refs from another repository
pull Fetch from and integrate with another repository or a local branch
push Update remote refs along with associated objects
'git help -a' and 'git help -g' list available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
pi@Sprinklers:~ $ git version
git version 2.11.0
ignore that ....I needed to change to /home/pi/SIP/future directory for it to fly
pi@Sprinklers:~ $ git checkout master
fatal: Not a git repository (or any of the parent directories): .git
pi@Sprinklers:~ $ cd SIP
pi@Sprinklers:~/SIP $ ls
backports data gv.pyc i18n.py plugins ReverseProxied.py sip.pyc _thread webpages.pyc
blinker future gv_reference.txt i18n.pyc pylcd.py ReverseProxied.pyc sip.service urls.py
cheroot gpio_pins.py helpers.py __init__.py pylcd.pyc sessions six.py urls.pyc
convert_progs.py gpio_pins.pyc helpers.pyc ospi.pyc README.md sip3.service static web
convert_progs.pyc gv.py i18n past reprlib sip.py templates webpages.py
pi@Sprinklers:~/SIP $ cd future
pi@Sprinklers:~/SIP/future $ ls
backports builtins __init__.py __init__.pyc moves standard_library tests types utils
pi@Sprinklers:~/SIP/future $ git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
pi@Sprinklers:~/SIP/future $
then sudo reboot and its once again alive.....thanks, bob.
pi@Sprinklers:~ $ git checkout master
fatal: Not a git repository (or any of the parent directories): .git
pi@Sprinklers:~ $ git
usage: git [--version] [--help] [-C <path>] [-c name=value]
[--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
[-p | --paginate | --no-pager] [--no-replace-objects] [--bare]
[--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
<command> [<args>]
These are common Git commands used in various situations:
start a working area (see also: git help tutorial)
clone Clone a repository into a new directory
init Create an empty Git repository or reinitialize an existing one
work on the current change (see also: git help everyday)
add Add file contents to the index
mv Move or rename a file, a directory, or a symlink
reset Reset current HEAD to the specified state
rm Remove files from the working tree and from the index
examine the history and state (see also: git help revisions)
bisect Use binary search to find the commit that introduced a bug
grep Print lines matching a pattern
log Show commit logs
show Show various types of objects
status Show the working tree status
grow, mark and tweak your common history
branch List, create, or delete branches
checkout Switch branches or restore working tree files
commit Record changes to the repository
diff Show changes between commits, commit and working tree, etc
merge Join two or more development histories together
rebase Reapply commits on top of another base tip
tag Create, list, delete or verify a tag object signed with GPG
collaborate (see also: git help workflows)
fetch Download objects and refs from another repository
pull Fetch from and integrate with another repository or a local branch
push Update remote refs along with associated objects
'git help -a' and 'git help -g' list available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
pi@Sprinklers:~ $ git version
git version 2.11.0
ignore that ....I needed to change to /home/pi/SIP/future directory for it to fly
pi@Sprinklers:~ $ git checkout master
fatal: Not a git repository (or any of the parent directories): .git
pi@Sprinklers:~ $ cd SIP
pi@Sprinklers:~/SIP $ ls
backports data gv.pyc i18n.py plugins ReverseProxied.py sip.pyc _thread webpages.pyc
blinker future gv_reference.txt i18n.pyc pylcd.py ReverseProxied.pyc sip.service urls.py
cheroot gpio_pins.py helpers.py __init__.py pylcd.pyc sessions six.py urls.pyc
convert_progs.py gpio_pins.pyc helpers.pyc ospi.pyc README.md sip3.service static web
convert_progs.pyc gv.py i18n past reprlib sip.py templates webpages.py
pi@Sprinklers:~/SIP $ cd future
pi@Sprinklers:~/SIP/future $ ls
backports builtins __init__.py __init__.pyc moves standard_library tests types utils
pi@Sprinklers:~/SIP/future $ git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
pi@Sprinklers:~/SIP/future $
then sudo reboot and its once again alive.....thanks, bob.