git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Why is it bad to rewind a branch that has already been pushed out?

From
Junio C Hamano <junkio@cox.net>
Date
Feb 4, 2007, 20:08 UTC
Message-ID
<7vlkjdr8hj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200702041716.39999.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> writes:
> Mention git-revert as an alternative to git-reset to revert changes.
Thanks; that makes sense.  Applied.

It is not a biggie but for future reference you might want to check your KMail configuration to avoid the wrapped line below:

Show 7 quoted lines
> diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
> index 5fc5be5..129c5c5 100644
> --- a/Documentation/tutorial.txt
> +++ b/Documentation/tutorial.txt
> @@ -461,6 +461,8 @@ this branch.  If this branch is the only branch containing 
> those
>  commits, they will be lost.  Also, don't use "git reset" on a
Previous: Robin RosenbergNext: Michael
Message 7 of 12 in “Why is it bad to rewind a branch that has already been pushed out?”
  1. Junio C HamanoFeb 3, 2007
  2. Andy ParkinsFeb 3, 2007
  3. Junio C HamanoFeb 3, 2007
  4. Andy ParkinsFeb 4, 2007
  5. Theodore TsoFeb 3, 2007
  6. Robin RosenbergFeb 4, 2007
  7. Junio C HamanoFeb 4, 2007
  8. Documentation: add KMail in SubmittingPatchesMichael, Feb 5, 2007
  9. Junio C HamanoFeb 6, 2007
  10. MichaelFeb 6, 2007
  11. Jakub NarebskiFeb 6, 2007
  12. Andy ParkinsFeb 6, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.