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

Re: Wrong code on master

From
JDJonathan Duncan <jonathan@memoryties.com>
Date
Dec 24, 2011, 06:37 UTC
Message-ID
<354A93E2-42C7-423D-BE99-1FDCF511741A@memoryties.com>
In-Reply-To
<op.v6zbsrvi0aolir@keputer>
On 23 Dec 2011, at 22:49, Frans Klaver wrote:
Show 5 quoted lines
> Well, the proper way is to revert the commits. That won't result in all other developers having to deal with a force-updated branch. If you can deal with it you can always
> 
> $ git push origin +branch
> 
> but I wouldn't consider that a nice thing to do.
Good information, thank you.  I think I will mark this as a good learning experience for me.  I will make it a point to inform all my team members to work from branches until we are ready for merging to the master branch.
Previous: Frans KlaverNext: Nathan W. Panike
Message 3 of 4 in “Wrong code on master”
  1. Jonathan DuncanDec 24, 2011
  2. Frans KlaverDec 24, 2011
  3. Jonathan DuncanDec 24, 2011
  4. Nathan W. PanikeDec 24, 2011

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.