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

refactoring in GIT

From
Eeugene <eugene@oggtrading.com>
Date
Jun 28, 2011, 13:19 UTC
Message-ID
<loom.20110628T151105-908@post.gmane.org>
Hi,
 I'm new to GIT and have two questions about code refactoring.

#1. I want to refactor class A into few classes B,C,D. How should I check them in and mark class A inactive so that development on A stops? Note, I do need A stay in repository for backward compt. with prior code releases.

#2. [related question] What if another developer already had A in his local repository, made changes and wants to commit after me. I just made A obsolete. Does he have drop his changes and take B,C,D from me and/or merge?

Sorry if this question was already answered, pls point me.

Thanks, Eugene

Next: Massimo Manca
Message 1 of 4 in “refactoring in GIT”
  1. eugeneJun 28, 2011
  2. Massimo MancaJun 28, 2011
  3. Christof KrügerJun 28, 2011
  4. Fredrik GustafssonJun 28, 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.