From: Avery Pennarun <apenwarr@gmail.com>
To: Marc Fournier <marc.fournier@camptocamp.com>
Cc: git@vger.kernel.org
Subject: Re: git-subtree: directory mismatch
Date: Tue, 24 Nov 2009 16:48:26 -0500 [thread overview]
Message-ID: <32541b130911241348s21e21fb8n12edf374e6a3c309@mail.gmail.com> (raw)
In-Reply-To: <20091124195353.GA16627@lonquimay.wrk.lsn.camptocamp.com>
On Tue, Nov 24, 2009 at 2:53 PM, Marc Fournier
<marc.fournier@camptocamp.com> wrote:
> I was not able to reproduce this bug in any of the following cases:
> - if the README file wasn't empty
> - if modules/cognac is renamed to something else
> - if modules/cognac doesn't have the same sub-directories than
> modules/mapserver
>
> This bug happens using git 1.5.5.6 as well as 1.6.5. It seems to happen
> when git-subtree calls "git merge -s subtree".
Yup. This is basically a bug in "git merge -s subtree": it guesses
which subtree to merge into, rather than actually taking a prefix
parameter. I've been meaning to either submit a patch for this, or
find a way to work around it.
This doesn't usually happen once your project is relatively mature
(ie. doesn't have blank or "default" template files in it) since then
the auto-guessing gets more reliable. But there's no good reason to
do the auto-guessing, so it would be best to do this "properly."
Sorry that I haven't had time to fix it yet...
Avery
next prev parent reply other threads:[~2009-11-24 21:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 19:53 git-subtree: directory mismatch Marc Fournier
2009-11-24 21:48 ` Avery Pennarun [this message]
2009-11-24 23:08 ` Nanako Shiraishi
2009-11-25 18:28 ` Avery Pennarun
2009-11-25 19:31 ` Junio C Hamano
2009-11-25 19:48 ` Avery Pennarun
2009-11-25 20:20 ` Junio C Hamano
2009-11-25 23:17 ` Johannes Schindelin
2009-11-25 23:20 ` Avery Pennarun
2009-11-25 23:41 ` Björn Steinbrink
2009-11-25 23:45 ` Avery Pennarun
2009-11-25 14:32 ` Marc Fournier
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=32541b130911241348s21e21fb8n12edf374e6a3c309@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=marc.fournier@camptocamp.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