From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Rene Herman" <rene.herman@keyaccess.nl>,
"Jan Engelhardt" <jengelh@computergmbh.de>,
git <git@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Josef Sipek" <jsipek@fsl.cs.sunysb.edu>
Subject: Re: [ANNOUNCE] Stacked GIT 0.14.2
Date: Mon, 24 Mar 2008 23:55:39 +0000 [thread overview]
Message-ID: <b0943d9e0803241655s7a7fea9cvcd3c162253e49625@mail.gmail.com> (raw)
In-Reply-To: <7vlk47ua3v.fsf@gitster.siamese.dyndns.org>
On 24/03/2008, Junio C Hamano <gitster@pobox.com> wrote:
> Rene Herman <rene.herman@keyaccess.nl> writes:
> > And I remember some mumblings about git growing quilt-like
> > functionality itself. Anything on that?
>
>
> Not my mumbling, but I am quite open to slurp in guilt as a subdirectory
> in git.git at some point in the future just like we bundle git-gui and
> gitk if asked by the maintainer.
>
> The same applies to StGIT for that matter, although I somehow feel that is
> much less likely to happen, because it lived long enough as a standalone
> project with enough following to achieve sustainable momentum by itself.
Indeed, StGIT has grown quite a lot (it now has ~45 commands) and it
probably feels better as a tool on its own. However, I think it would
be good for git to get such functionality (and it could even share
some ideas StGIT and guilt). If this functionality will get fully
integrated in git, StGIT could use it directly rather than the
low-level git commands.
An example of additional functionality that might stay outside of git
(at least for a while): since basic patch management support is pretty
much complete in StGIT, a feature we are thinking about adding is
better support for patch sharing between developers (or
repositories/branches). This should allow easier cloning and merging
with branches that have a volatile history at the top.
--
Catalin
next prev parent reply other threads:[~2008-03-24 23:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 19:59 [ANNOUNCE] Stacked GIT 0.14.2 Catalin Marinas
2008-03-24 20:15 ` Jan Engelhardt
2008-03-24 20:33 ` Rene Herman
2008-03-24 20:43 ` Junio C Hamano
2008-03-24 22:31 ` Rene Herman
2008-03-24 22:50 ` Catalin Marinas
2008-03-24 23:23 ` Rene Herman
2008-03-24 23:40 ` Catalin Marinas
2008-03-24 23:55 ` Josef Sipek
2008-03-25 9:50 ` slurping in guilt, was " Johannes Schindelin
2008-03-26 21:24 ` Junio C Hamano
2008-03-27 0:03 ` Josef Sipek
2008-03-24 23:55 ` Catalin Marinas [this message]
2008-03-24 23:24 ` Catalin Marinas
2008-03-24 23:39 ` Josef Sipek
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=b0943d9e0803241655s7a7fea9cvcd3c162253e49625@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jengelh@computergmbh.de \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
/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).