From: "David Symonds" <dsymonds@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
"git mailing list" <git@vger.kernel.org>
Subject: Re: on subtree checkout
Date: Mon, 25 Feb 2008 18:30:36 -0800 [thread overview]
Message-ID: <ee77f5c20802251830p47c6de60je97a31cb34bc3105@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0802260156350.3322@eeepc-johanness>
On Mon, Feb 25, 2008 at 5:59 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>
> On Sun, 24 Feb 2008, Nguyen Thai Ngoc Duy wrote:
>
> > I'm going to implement subtree checkout. The plan is to save "index
> > prefix" in GIT_DIR/prefix and update git commands to use index prefix
> > when accessing the index. If I'm heading a wrong way, stop me now.
>
> As I wrote a long time ago already, I think the correct approach would be
> to reuse the code for the core.ignoreStat feature.
>
> But I agree with others that you should think about sane implementations
> of rebase/merge with partial checkouts.
I, too, was shortly going to attempt a partial checkout/clone
implementation. The intended context of my implementation was similar
to the KDE scenario in that you might only care about /pkgA and /pkgB,
so changes to /pkgC are usually irrelevant and independent to your
work-flow, so I was planning to assume a simplistic "theirs" merge
strategy for /pkgC, etc.
Dave.
next prev parent reply other threads:[~2008-02-26 2:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 9:34 on subtree checkout Nguyen Thai Ngoc Duy
2008-02-24 9:59 ` Robin Rosenberg
2008-02-24 10:23 ` Jakub Narebski
2008-02-24 10:53 ` Robin Rosenberg
2008-02-24 11:53 ` Jakub Narebski
2008-02-24 10:03 ` Jakub Narebski
2008-02-24 15:12 ` Nguyen Thai Ngoc Duy
2008-02-24 15:45 ` Jakub Narebski
2008-02-24 15:59 ` Matthieu Moy
2008-02-24 17:22 ` Robin Rosenberg
2008-02-26 1:59 ` Johannes Schindelin
2008-02-26 2:30 ` David Symonds [this message]
2008-02-26 11:23 ` Johannes Schindelin
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=ee77f5c20802251830p47c6de60je97a31cb34bc3105@mail.gmail.com \
--to=dsymonds@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pclouds@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).