From: Junio C Hamano <gitster@pobox.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: Pat Thoyts <patthoyts@googlemail.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-gui: document the gui.maxfilesdisplayed variable
Date: Sun, 13 Feb 2011 23:51:04 -0800 [thread overview]
Message-ID: <7v39nruk9j.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 20110213125324.GA31986@book.hvoigt.net
Heiko Voigt <hvoigt@hvoigt.net> writes:
> I am not sure how we should go about this patch. Should I split it in
> two since it removes the TODO line in git-gui and adds the
> documentation in git?
Two opposing thoughts.
1. We can keep git-gui and git proper separate projects, move git-gui
documentation out of git to git-gui, and with clever Makefile trick
include and build git-gui related documentation conditionally only
when git-gui appears part of the git project tree (this anticipates a
future where git-gui is bound to git not with the subtree merge
strategy as we currently do, but as a submodule).
2. Just like the Linux kernel project, we can make each subsystem with
separate maintainers just different repositories of the same git
project with their own focus. We already do this for git-svn (which I
delegate to Eric Wong by pulling from him) and some parts of contrib/
tree; we have already been halfway there for gitweb/ (which I don't
regularly "pull from", but I mainly act as a patch monkey without
actively managing that part myself). I don't see why we cannot extend
that model to git-gui and gitk.
next prev parent reply other threads:[~2011-02-14 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 12:53 [PATCH] git-gui: document the gui.maxfilesdisplayed variable Heiko Voigt
2011-02-14 7:51 ` Junio C Hamano [this message]
2011-02-14 22:03 ` future of git-gui as subsytem or submodule, WAS: " Heiko Voigt
2011-02-14 22:17 ` future of git-gui as subsytem or submodule Jonathan Nieder
2011-02-14 22:46 ` future of git-gui as subsytem or submodule, WAS: [PATCH] git-gui: document the gui.maxfilesdisplayed variable Jens Lehmann
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=7v39nruk9j.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=patthoyts@googlemail.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).