[sorry for top post - had to recondtruct the email]
Much of the firestorm was about Filippe's use case, with a little bit of reluctance to actually document Git ;-)

Plus the '.' represents 'the thing you are working on / thinking about', so if the parameter is meant to be a remote repo, then it's the current repo. If its a file path parameter then its the current directory.

I'm not sure if there are any command that include both a remote parameter and a file parameter option that would get confusing (as if it isn't confusing enough!)

Git does have a lot of instructions that sound like "turn left 300 meters before where the old church used to be" (and they've relaid the junction so it feels like a straight on)....

I don't use 'pull' because of the potential issues. It's easier to fetch, and then fudge from there with forced fast forward etc (transferring work from Windows netbook to a hack ubuntu laptop whose graphics chip packs in every month or two)


----- Original Message ----- From: "Yawar Amin" <yawar.a...@gmail.com>
To: <git-users@googlegroups.com>
Cc: "Philip Oakley" <philipoak...@iee.org>
Sent: Friday, May 24, 2013 1:56 AM
Subject: Re: [git-users] Re: proper meaning of '.' dot in a git command?


On 2013-05-23 15:33, Philip Oakley wrote:
I did find part of the documentation hidden in git config as a special
case for defining a remote, but the command line effect hadn't been
noted. So I've submitted a documentation patch for comment to the main

Indeed, it's set off quite a firestorm :-)

FWIW I still believe that `.' means only `the local repository', and not
`the current directory which may or may not contain a .git directory'.

You can run a simple git push in a subdirectory of a repository root
directory to prove this to yourself:

(Assuming a throwaway test repo for the below commands)

git checkout -b mybranch master
mkdir mydir
cd mydir
echo myword >myword.txt
git add myword.txt
git commit -m"My message"
git push .. mybranch:master # fatal: '..' does not appear to be a...
git push . mybranch:master # Total 0 (delta 0), reused 0 (delta 0)...

True. Though often an extended discussion...

        in [PATCH 1/3] fetch: add --allow-local option,

I tend to agree with Junio that the existing _default_ fetch behaviour
shouldn't be changed. But disagreement can be vocal sometimes....



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.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to