git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Clemence <matthew.clemence@virgin.net>
To: git@vger.kernel.org
Subject: Suggested workflow for frequent directory renames.
Date: Tue, 26 May 2009 01:17:48 +0100	[thread overview]
Message-ID: <4A1B352C.9030409@virgin.net> (raw)

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

             reply	other threads:[~2009-05-26  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26  0:17 Matthew Clemence [this message]
2009-05-26  9:24 ` Suggested workflow for frequent directory renames Jakub Narebski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A1B352C.9030409@virgin.net \
    --to=matthew.clemence@virgin.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).