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

Suggested workflow for frequent directory renames.

From
MCMatthew Clemence <matthew.clemence@virgin.net>
Date
May 26, 2009, 00:17 UTC
Message-ID
<4A1B352C.9030409@virgin.net>
Dear git users,

I am working with an externally supplied code tree (some 2000 files, which gets passed to me without any SCM) and have multiple users wokring on their own individual branched versions under git control. The problem I am facing is that there are frequenct directory renames when the code updates which I need to find a relatively painless way of bringing the users branches up to date. From reading the lists and faq, there seems to be problems (and strong opinions) with this, and I am struggling to find an effcient model to manage this merging - either git loses track of the users changed files (and so have to be manually merged from diff files and usually lose history) or git loses track of everything else (and I end up manually adding files from the new tree to get out of merge conflict).

I would be very interested to hear if anyone has a suggestion on how this could best be handled.

Many thanks
Matthew
Next: Jakub Narebski
Message 1 of 2 in “Suggested workflow for frequent directory renames.”
  1. Matthew ClemenceMay 26, 2009
  2. Jakub NarebskiMay 26, 2009

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.