From: "H. Peter Anvin" <hpa@zytor.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Tracking files across tree reorganizations
Date: Thu, 15 Dec 2005 00:12:14 -0800 [thread overview]
Message-ID: <43A1255E.50400@zytor.com> (raw)
In-Reply-To: <46a038f90512142138x77e57850ib095c1d68ecdfd13@mail.gmail.com>
Martin Langhoff wrote:
> On 12/15/05, H. Peter Anvin <hpa@zytor.com> wrote:
>
>>Did anything ever happen with that?
>
> Perhaps I'm slow today, but git-merge -s recursive was supposed to do
> it transparently (automagically). At least it was merged into git with
> that excuse ;-)
>
> Does it not work for you or am I missing something?
>
I'll try it.
-hpa
prev parent reply other threads:[~2005-12-15 8:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 21:15 Tracking files across tree reorganizations H. Peter Anvin
2005-12-14 22:36 ` Petr Baudis
2005-12-14 23:12 ` H. Peter Anvin
2005-12-14 23:45 ` Petr Baudis
2005-12-14 23:47 ` H. Peter Anvin
2005-12-14 23:39 ` Linus Torvalds
2005-12-14 23:44 ` H. Peter Anvin
2005-12-15 0:36 ` Junio C Hamano
2005-12-15 1:02 ` H. Peter Anvin
2005-12-15 1:44 ` Petr Baudis
2005-12-15 5:40 ` Martin Langhoff
2005-12-15 5:38 ` Martin Langhoff
2005-12-15 8:12 ` H. Peter Anvin [this message]
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=43A1255E.50400@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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).