git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Thomas Taranowski <tom@baringforge.com>,
	git <git@vger.kernel.org>,
	"David A. Greene" <greened@obbligato.org>,
	Stephen Smith <ishchis2@gmail.com>
Subject: Re: git subtree oddity
Date: Thu, 28 Mar 2013 17:34:53 +0100 (CET)	[thread overview]
Message-ID: <1827202810.1012362.1364488493363.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <7v38vfwlxv.fsf@alter.siamese.dyndns.org>

> 
> I am starting to regret that I caved in and started carrying a copy
> of it in contrib/.  It probably is a good idea to drop it from my
> tree and let it mature and eventually flourish outside.
> 

that's a shame... it solves a real problem, is simple to use, and really powerfull. 

but unfortunately, I have sent a patch that solves a serious bug... which had already been reported and patched but had received no answer, and nobody replied to it.

Is there anything that can be done to get this rolling, or a way to have the use-case it covers better handle by git-submodule ?


currently the problem of a git repo in a git repo is very complicated to deal with in a clean way...


Regards

Jérémy

  reply	other threads:[~2013-03-28 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  3:12 git subtree oddity Thomas Taranowski
2013-03-28 13:34 ` Stephen Smith
2013-03-28 16:03   ` Junio C Hamano
2013-03-28 16:34     ` Jeremy Rosen [this message]
2013-03-28 19:29       ` Thomas Taranowski
2013-03-28 19:44         ` Thomas Taranowski
2013-03-29  5:47       ` Junio C Hamano

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=1827202810.1012362.1364488493363.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=greened@obbligato.org \
    --cc=ishchis2@gmail.com \
    --cc=tom@baringforge.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).