From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git wiki
Date: Fri, 05 May 2006 08:26:52 +0200 [thread overview]
Message-ID: <e3er79$6s4$1@sea.gmane.org> (raw)
In-Reply-To: 20060505062236.GA4544@c165.ib.student.liu.se
Fredrik Kuivinen wrote:
> On Thu, May 04, 2006 at 08:56:59PM -0400, linux@horizon.com wrote:
>> What people who are asking for explicit rename tracking actually want
>> is automatic rename merging. If branch A renames a file, and branch B
>> corrects a typo on a comment somewhere, they'd like the merge to
>> both patch and rename the file. If you can do that, you have met the
>> need, even if your solution isn't the one the feature requester
>> imagined.
>
> I don't know if you already know this, if you do it might be valuable
> for other readers.
>
> If the rename is detected by the current rename detection code
> (git-diff-tree -M) then the merge case described above is handled
> perfectly fine by the current git. That is, the rename is followed and
> the patch fixing the typo is applied to the renamed file. This assumes
> that the default merge strategy (recursive) is used.
And if you do 'commit - rename, no changes - commit' sequence then rename
will be detected.
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-05 6:27 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 0:56 [ANNOUNCE] Git wiki linux
2006-05-05 6:22 ` Fredrik Kuivinen
2006-05-05 6:26 ` Jakub Narebski [this message]
2006-05-05 9:23 ` Petr Baudis
2006-05-05 9:51 ` Junio C Hamano
2006-05-05 16:40 ` Petr Baudis
2006-05-05 16:47 ` Jakub Narebski
2006-05-05 18:49 ` Jakub Narebski
2006-05-05 16:36 ` Petr Baudis
2006-05-05 17:48 ` Linus Torvalds
2006-05-05 19:04 ` Dave Jones
2006-05-05 18:15 ` Petr Baudis
2006-05-05 18:20 ` Petr Baudis
2006-05-05 18:27 ` Jakub Narebski
2006-05-05 18:31 ` Linus Torvalds
2006-05-05 18:54 ` Petr Baudis
2006-05-05 19:39 ` Jakub Narebski
2006-05-06 13:37 ` Jakub Narebski
2006-05-05 19:49 ` Junio C Hamano
2006-05-06 6:53 ` Martin Langhoff
2006-05-06 7:14 ` Junio C Hamano
2006-05-06 7:33 ` Jakub Narebski
2006-05-06 7:41 ` Junio C Hamano
2006-05-06 12:46 ` Bertrand Jacquin
2006-05-05 20:45 ` Olivier Galibert
-- strict thread matches above, loose matches on Subject: below --
2006-05-02 23:25 Petr Baudis
2006-05-02 23:33 ` Junio C Hamano
2006-05-03 8:39 ` Paolo Ciarrocchi
2006-05-03 9:00 ` Petr Baudis
2006-05-03 9:13 ` Paolo Ciarrocchi
2006-05-03 13:41 ` Nicolas Pitre
2006-05-03 14:29 ` Shawn Pearce
2006-05-03 15:01 ` Andreas Ericsson
2006-05-03 15:24 ` Paolo Ciarrocchi
2006-05-03 15:30 ` Jakub Narebski
2006-05-03 15:30 ` Linus Torvalds
2006-05-03 15:39 ` Paolo Ciarrocchi
2006-05-03 16:06 ` Linus Torvalds
2006-05-03 16:17 ` Jakub Narebski
2006-05-03 16:19 ` Paolo Ciarrocchi
2006-05-03 16:46 ` Jakub Narebski
2006-05-03 19:21 ` David Lang
2006-05-03 19:30 ` Petr Baudis
2006-05-03 19:46 ` David Lang
2006-05-03 20:07 ` Petr Baudis
2006-05-04 0:53 ` Daniel Barkalow
2006-05-03 16:47 ` Theodore Tso
2006-05-03 17:06 ` Linus Torvalds
2006-05-03 17:15 ` Theodore Tso
2006-05-03 17:40 ` Linus Torvalds
2006-05-03 22:39 ` Sam Ravnborg
2006-05-03 22:46 ` Petr Baudis
2006-05-03 22:50 ` Joel Becker
2006-05-03 23:05 ` Petr Baudis
2006-05-03 18:04 ` Daniel Barkalow
2006-05-03 18:45 ` sean
2006-05-03 18:45 ` sean
2006-05-03 20:58 ` Junio C Hamano
2006-05-03 21:01 ` Junio C Hamano
2006-05-03 22:13 ` Linus Torvalds
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='e3er79$6s4$1@sea.gmane.org' \
--to=jnareb@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.