From: Adam Spiers <git@adamspiers.org>
To: Drew Northup <n1xim.email@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
felipe.contreras@gmail.com,
"Jason J Pyeron CTR (US)" <jason.j.pyeron.ctr@mail.mil>
Subject: Re: splitting off shell test framework
Date: Mon, 12 Nov 2012 23:09:56 +0000 [thread overview]
Message-ID: <CAOkDyE9phgZ4ToWTWa2GYgfVkDknCqWr+KEyqVoHg0RVrVVk9A@mail.gmail.com> (raw)
In-Reply-To: <CAM9Z-n=ypt_fyFcPjYD28NNoxnJ2ZSovd1TbERdA8RJY1Va=kA@mail.gmail.com>
On Mon, Nov 12, 2012 at 6:18 PM, Drew Northup <n1xim.email@gmail.com> wrote:
> On Mon, Nov 12, 2012 at 11:37 AM, Adam Spiers <git@adamspiers.org> wrote:
>> As it turned out to be fairly easy, I was wondering if there would be
>> any interest in doing this more formally, i.e. splitting off the
>> framework so that it could be used and improved outside the scope of
>> git development? Of course this would pose the question how git would
>> consume this new project without any risk of destabilisation. I'm
>> guessing that simply using a git submodule would solve the problem,
>> but ICBW ...
>>
>> Just an idea. Interesting, or terrible? :)
>
> Done at least once already:
>
> http://comments.gmane.org/gmane.comp.version-control.git/201591
Nice! So hopefully someone will submit patches to build a two-way bridge
via git subtree. Having them diverge would be sad.
next prev parent reply other threads:[~2012-11-12 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 16:37 splitting off shell test framework Adam Spiers
2012-11-12 16:44 ` Felipe Contreras
2012-11-12 16:57 ` Pyeron, Jason J CTR (US)
2012-11-12 18:18 ` Drew Northup
2012-11-12 23:09 ` Adam Spiers [this message]
2017-08-23 13:46 ` Adam Spiers
2017-08-23 15:47 ` Jeff King
2017-08-23 23:23 ` Adam Spiers
2017-08-24 14:23 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOkDyE9phgZ4ToWTWa2GYgfVkDknCqWr+KEyqVoHg0RVrVVk9A@mail.gmail.com \
--to=git@adamspiers.org \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=jason.j.pyeron.ctr@mail.mil \
--cc=n1xim.email@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).