Pursuer wrote in
 <[email protected]>:
 |Thanks a lot for your rearranging and advice.
 |
 |by the way&nbsp;I'm sure I only add tcc.h to the commit "misplaced \
 |parenthese around...", So I'm also confused about the side-effect mentio\
 |ned by&nbsp;Christian Jullien. (In fact I had cloned a new copy before \
 |rearranging, In which the&nbsp;additions made by Kyryl on 22_floating_po\
 |int.c was not removed.)

You do not need to reclone a repository normally, there are
a couple of ways to reset your own branches to the origin that is
stored in the database.
That is to say, do not overcomplicate it, these are just commits
stacking upon each other from toe to tip, and the tip is mob here.
You can plug and play them around and stick together almost at
will.  (Almost because the very first commit of a branch is not so
easy.)

  git checkout -B mob origin/mob

Checks out to local branch mob, resetting it first as necessary,
and lets it track themob branch of the upstream "origin".

  git update-ref refs/heads/mob origin/mob

Should just make the reference "mob" re-point to something.
Note you really need refs/heads/, because git lets "you go
outside" too, which can be surprising.

  git reset -q --hard origin/mob

Is also an idea.  But i would recommend the first.
You can see all the tips mentioned above like that

  git log --color=auto --no-walk --decorate --oneline --branches --remotes

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to