Groups | Search | Server Info | Login | Register
Groups > comp.os.linux.misc > #77819
| From | ram@zedat.fu-berlin.de (Stefan Ram) |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: basic git operations |
| Date | 2025-11-22 20:10 +0000 |
| Organization | Stefan Ram |
| Message-ID | <dot-20251122210318@ram.dialup.fu-berlin.de> (permalink) |
| References | <git-20251122190040@ram.dialup.fu-berlin.de> <10ft49n$ii0$1@reader2.panix.com> |
pa@see.signature.invalid (Pierre Asselin) wrote or quoted:
>With a dot after "git init" ?
I inadvertently added the dot when using "add ." as a template
for the init command. I have since removed this dot ".", but it
seems to not have done any harm.
Some git tutorials do not address things that are confusing for
me as a beginner such as:
- They sometimes speak of the "working directory". Then, when you
get an error message containing "work tree", you wonder: "Is this
the same thing as the 'working directory'?". For now, I assume:
yes.
- They tell you about adding files to the staging area. But for me
it was not clear whether this is a copy with all data or just a
link to the file in the work tree. Now, the chatbot told me that
it's a full copy with all data in the staging area. So, when you
later change your work file, it will not be reflected in the staging
area without another "add". Of course, as a beginner, next thing
you wonder then, is whether this will replace the previous copy
in the staging area (I guess so) or be added as a second copy . . .
Having learned about the environment variable "GIT_WORK_TREE" actually
is helping me, because I wanted a git directory that is different from
my work tree anyway, so now I know how to do it. (Before this, I would
copy all my files from my working directory to the git directory,
adding and committing and then deleting them.) I want the git
directory to be on a different disk than the work tree, because it's
intended to be a backup.
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
basic git operations ram@zedat.fu-berlin.de (Stefan Ram) - 2025-11-22 18:08 +0000
Re: basic git operations Richard Kettlewell <invalid@invalid.invalid> - 2025-11-22 18:33 +0000
Re: basic git operations ram@zedat.fu-berlin.de (Stefan Ram) - 2025-11-22 18:46 +0000
Re: basic git operations ram@zedat.fu-berlin.de (Stefan Ram) - 2025-11-22 20:34 +0000
Re: basic git operations ram@zedat.fu-berlin.de (Stefan Ram) - 2025-11-22 21:13 +0000
Re: basic git operations Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-22 21:59 +0000
Re: basic git operations Richard Kettlewell <invalid@invalid.invalid> - 2025-11-22 23:11 +0000
Re: basic git operations pa@see.signature.invalid (Pierre Asselin) - 2025-11-22 19:52 +0000
Re: basic git operations ram@zedat.fu-berlin.de (Stefan Ram) - 2025-11-22 20:10 +0000
Re: basic git operations Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-22 21:57 +0000
Re: basic git operations Beej Jorgensen <beej@beej.us> - 2025-11-24 20:23 +0000
Re: basic git operations ram@zedat.fu-berlin.de (Stefan Ram) - 2025-11-24 20:38 +0000
Re: basic git operations Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-24 23:37 +0000
Re: basic git operations Beej Jorgensen <beej@beej.us> - 2025-11-25 22:06 +0000
Re: basic git operations Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-26 00:53 +0000
Re: basic git operations Pancho <Pancho.Jones@protonmail.com> - 2025-11-22 20:00 +0000
Re: basic git operations ram@zedat.fu-berlin.de (Stefan Ram) - 2025-11-22 20:19 +0000
Re: basic git operations Pancho <Pancho.Jones@protonmail.com> - 2025-11-22 20:24 +0000
Re: basic git operations ram@zedat.fu-berlin.de (Stefan Ram) - 2025-11-22 20:37 +0000
Re: basic git operations Beej Jorgensen <beej@beej.us> - 2025-11-24 19:51 +0000
Re: basic git operations Richard Kettlewell <invalid@invalid.invalid> - 2025-11-24 22:27 +0000
Re: basic git operations Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-24 23:41 +0000
csiph-web