Hi!
When I do
>git clone /some_local_git_repo/
and then compare the remote branches of the using
>git log origin/master
on the cloned repo and my new repo, the logs are different, why is
this?
I thought the log seen by the two repos on origin/master should be the
same since "git clone" accordin
Hi,
The log should be the same. You are looking at the logs of two different
things:
repository A (some_local_git_repo)
- has a remote called "origin" which is where it was originally cloned from
(github? some server?)
repository B (your local clone)
- has a remote called "origin" which is re
Eh, please ignore my first sentence: "The log should be the same." - I left
it in there by mistake.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/git-users/-/RI
Great, thanks for your answer!
A confusing thing is the difference between:
>git log master
and
>git log origin/master
"git log master" shows the log of the remote repositorys master
branch.
"git log origin/master" shows the log of a _local_ branch which is
tracking a remote branch (it is track
On Friday, January 20, 2012 4:01:27 PM UTC+1, dspfun wrote:
>
> Great, thanks for your answer!
>
> A confusing thing is the difference between:
>
> >git log master
> and
> >git log origin/master
>
> "git log master" shows the log of the remote repositorys master
> branch.
>
No. "git log mas
On Fri, 20 Jan 2012 07:01:27 -0800 (PST)
dspfun wrote:
> A confusing thing is the difference between:
>
> >git log master
> and
> >git log origin/master
>
> "git log master" shows the log of the remote repositorys master
> branch.
>
> "git log origin/master" shows the log of a _local_ branch w
Hi,
Here is a break down of a problem I currently face: I create a patch
from the last two commits, reset to two versions before and apply the
patch. I tried to do the same on a new git repository and it does work
with the same sequence of commands. But on my submodule I get the
following error:
I can't recreate the problem.
If I do some local commits with lots of whitespaces in them, it works fine.
If I do format-patch with --ignore-space-change, I am able to trigger a
similar error like the one you got.
Normally dealing with whitespaces isn't a problem in my experience.. Could
it be