All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin Wiśnicki" <mwisnicki@gmail.com>
To: git@vger.kernel.org
Subject: Re: Merge after directory rename ?
Date: Mon, 22 Aug 2011 00:32:54 +0000 (UTC)	[thread overview]
Message-ID: <j2s83l$eqg$1@dough.gmane.org> (raw)
In-Reply-To: CAMOZ1Bt8cP146xiDXfSA-naSOaS3AC8pUZgW12=3TMg2JGCD=w@mail.gmail.com

On Sun, 21 Aug 2011 23:53:34 +0000, Michael Witten wrote:
> Importantly, note that I used only file names in my example,
> specifically:
> 
>   5. [master]  rename dir1/file3 to dir3/file3
> 
> rather than mirroring your example by writing:
> 
>   5. [master]  rename dir1 to dir3
> 
> This is because git fundamentally tracks content, and paths are just one
> kind of content associated with another blob of content. Consequently,

I know it tracks content, yet it puts effort to detect file renames.
I want it to also detect directory renames, detecting it should be quite 
easy.

> git really knows next to nothing about directories, so it's not too
> surprising that git doesn't bother finding such a DIRECTORY rename
> anyway (at most, git would detect a FILE rename, and your FILE
> `dir1/file2' has nothing to do with, say, the FILE `dir1/file1' being
> renamed `dir2/file1').
> 
> Still, some command line switches could be useful to help the user
> express to git what should be going on in a case such as yours.

I would prefer it to be fully automatic :)
Or at least detect/warn about tree conflict.
Directory renames can happen quite frequently when working with Java/C# 
and it is unreasonable to expect that lazy user will have to keep track of 
it manually (with huge number of files it's impossible).

  reply	other threads:[~2011-08-22  0:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-21 21:41 Merge after directory rename ? Marcin Wiśnicki
2011-08-21 23:45 ` Michael Witten
2011-08-21 23:53   ` Michael Witten
2011-08-22  0:32     ` Marcin Wiśnicki [this message]
2011-08-22  2:19       ` Michael Witten
2011-08-22  8:49         ` Marcin Wiśnicki
2011-08-23 14:50           ` Michael Witten
2011-08-23 19:13     ` Jeff King

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='j2s83l$eqg$1@dough.gmane.org' \
    --to=mwisnicki@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.