[PATCH] Re: push: point to 'git pull' and 'git push --force' in case of non-fast forward

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Nicolas Sebrecht
Date: Thursday, August 6, 2009 - 2:16 pm

The 06/08/09, Junio C Hamano wrote:


I believe that this sentence a bit too much scaring for the beginner.
There are two kinds of update (push and pull). We loose history only
when pushing. I know this applies to Documentation/git-push.txt but out
of this context (and because we talk about pull near from here), I think
it would be clearer to say something like:

	In contrast, a non-fast-forward push will loose history.


<...>


Wouldn't "git pull --rebase" loose B? Shouldn't we have this

  ----------------
  
            D
           /
   ---X---A
  
  ----------------

instead?

-- 
Nicolas Sebrecht
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] Re: push: point to 'git pull' and 'git push --forc ..., Nicolas Sebrecht, (Thu Aug 6, 2:16 pm)
[RFC/PATCH 0/4] make helpful messages optional, Jeff King, (Sat Sep 5, 11:44 pm)
[PATCH 2/4] push: re-flow non-fast-forward message, Jeff King, (Sat Sep 5, 11:47 pm)
Re: [RFC/PATCH 0/4] make helpful messages optional, Matthieu Moy, (Sun Sep 6, 4:53 am)
[PATCH 0/2] configurable advice messages, Jeff King, (Wed Sep 9, 4:26 am)