Hi Christopher,
Git is funny because it is not centralised, so when you say the repo is
on the server, it is also likely that you have a local copy on your hard
drive (or SSD), unless that is you are using a mapped drive and working
directly on that e.g. a P: (project) drive.
You will find that immediately inside your project's directory there is
a '.git' (hidden) directory which is your local copy of the repository
(e.g. in your C:/myproject/ directory).
If your project is on your local drive then you are likely to also have
a copy of the project on the network server, which you keep up to date
with push/fetch/pull as and when you want to tell your world of the
latest developments.
Your directory structure should only have one single version (revision)
of the project present at one time (but *). It is easy to think that if
you need to compare two revisions you will need duplicated folders. This
shouldn't be necessary.
Git can diff between branches and revisions quite happily (I also use
the gitk viewer as a good way of wandering around the history when I'm
unsure what happened when/where).
Branches are a way of having separate lines of development that _you can
swap between_ and git will very quickly do that swap (i.e. less than
network transit time as it uses that local copy in .git to change over
the files that are different). This ability to swap takes a while to get
used to if you have a long history of using duplicated directories (old
habits die hard)
(*) Git now doe have a 'worktree' facility so you can have a primary
revision in your main worktree, and then have other revisions in other
named worktrees - each is considered independently.
You will also come across the fact that your local repo has a full copy
of everything from the server at the last time you looked, sort of
hidden away under "remote tracking branches (rtb)", which obviously
track the branches on the remote. While they look like they are
'special', they are not. It takes a while to grasp how to use them
effectively (i.e. _not_ needing to copy the rtb to a local branch of the
same name just to look at it.)
So, check where the copies of your repo are located. You may have one
locally, and one on a network server.
Only have the primary (your work) copy of the project in the repository
directory (rather than many), unless you read up on the 'worktree'
command (https://git-scm.com/docs/git-worktree).
Philip
On 18/08/2019 19:31, CrestChristopher wrote:
The Operating system is Windows10 (1903) the repository is on a
server; it's more or less a private server, there is two but the other
is not setup, yet.
What do you mean by directory structure ?
I'm someone who wants to organize their code and versions as I work on
coding projects and the like. I caught onto git late, but better late
then never.
Christopher
On 8/16/2019 9:01 AM, Philip Oakley wrote:
Chris,
Could you give a bit more background on your operating system,
working environment (are you an a networked system), where the
repository is / was (e.g. Github vs local), along with you directory
structure etc.
It feels like at the moment you are at the 'confused new user' stage
and are mixing together many different issues.
You could also include a little background as to how/why you got into
Git (e.g. you are a young screenwriter needing to keep back copies of
all your revisions, and multiple alternate write ups; or an older
mechanical engineer who is starting to dabble in coding and someone
said you need to use Git), as it would help the helpers guess what
things and analogies you will understand, and which things to steer
clear of.
Philip
On Thursday, August 15, 2019 at 2:53:28 AM UTC+1, CrestChristopher
wrote:
I have supposedly created the repository and mistakenly cloned the
repository, how do I access the repository though the shell (SSH) by
means of command prompt with git bashed installed, I probably
have to be
logged into the shell, if that is the case, no problem.
Christopher
--
You received this message because you are subscribed to the Google
Groups "Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to git-users+unsubscr...@googlegroups.com
<mailto:git-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/7e107db0-f9eb-4d8e-be02-d29f0c40632c%40googlegroups.com
<https://groups.google.com/d/msgid/git-users/7e107db0-f9eb-4d8e-be02-d29f0c40632c%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to git-users+unsubscr...@googlegroups.com
<mailto:git-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/7b67deae-5922-69cd-0aee-2d2d53d56dfe%40gmail.com
<https://groups.google.com/d/msgid/git-users/7b67deae-5922-69cd-0aee-2d2d53d56dfe%40gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/46ea5d1c-bb6b-9691-619a-3cbe4d5e7816%40iee.email.
