From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Git Mailing List <git@vger.kernel.org>,
Johan Herland <johan@herland.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Andy Parkins <andyparkins@gmail.com>
Subject: git-gui and gitk-git as submodules (Re: [RFC PATCH 0/2] Teach "git status" the "--ignore-submodules" option)
Date: Fri, 25 Jun 2010 14:01:47 -0500 [thread overview]
Message-ID: <20100625190147.GA17493@burratino> (raw)
In-Reply-To: <7vlja3j7hu.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> It would be reassuring to hear from
> people who are heavier submodule users than me, though...
Speaking of which, what ever came of the submodule dogfood experiment?
Given a patch to automatically resolve submodule-ejection/subtree-merge
conflicts, do you think a patch series to split off gitk and git-gui
as submodules could live in pu eventually?
Jonathan
next prev parent reply other threads:[~2010-06-25 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 14:55 [RFC PATCH 0/2] Teach "git status" the "--ignore-submodules" option Jens Lehmann
2010-06-25 14:56 ` [PATCH 1/2] git submodule: ignore dirty submodules for summary and status Jens Lehmann
2010-06-25 14:56 ` [PATCH 2/2] Add the option "--ignore-submodules" to "git status" Jens Lehmann
2010-06-25 18:24 ` [RFC PATCH 0/2] Teach "git status" the "--ignore-submodules" option Junio C Hamano
2010-06-25 19:01 ` Jonathan Nieder [this message]
2010-06-26 4:44 ` git-gui and gitk-git as submodules (Re: [RFC PATCH 0/2] Teach "git status" the "--ignore-submodules" option) Tay Ray Chuan
2010-06-26 11:45 ` Jens Lehmann
2010-06-26 18:31 ` git-gui and gitk-git as submodules Jonathan Nieder
2010-06-28 18:58 ` Jens Lehmann
2010-06-28 18:29 ` git-gui and gitk-git as submodules (Re: [RFC PATCH 0/2] Teach "git status" the "--ignore-submodules" option) Marc Branchaud
2010-06-28 19:00 ` Jens Lehmann
2010-06-28 19:55 ` Marc Branchaud
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=20100625190147.GA17493@burratino \
--to=jrnieder@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
/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).