From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Hackontest ideas?
Date: Tue, 29 Jul 2008 08:55:32 +0700 [thread overview]
Message-ID: <fcaeb9bf0807281855w3b06f624q18f5ac76a3bb405c@mail.gmail.com> (raw)
In-Reply-To: <20080729011404.GI32184@machine.or.cz>
On 7/29/08, Petr Baudis <pasky@suse.cz> wrote:
> On Mon, Jul 28, 2008 at 05:55:45PM -0700, Junio C Hamano wrote:
> > Petr Baudis <pasky@ucw.cz> writes:
> >
> > > (What feature in Git or a Git-related tool would you implement, given 24
> > > hours staight and unlimited pizza supply?)
> >
> > "Use 'assume unchanged' bit to implement narrow checkout".
>
>
> I think Nguyen Thai Ngoc Duy is already working on this? (Though I think
> he does not use the assume unchanged bit; but this will be likely done
> before the end of September.)
You are welcome to do ;) I got to narrow checkout from subtree
checkout where 'assume unchanged' bit was unapplicable so my approach
is a bit different, but probably 'assume unchanged' bit is the right
way to go.
--
Duy
next prev parent reply other threads:[~2008-07-29 1:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 0:01 Hackontest ideas? Petr Baudis
2008-07-29 0:10 ` Miklos Vajna
2008-07-29 5:31 ` Shawn O. Pearce
2008-07-29 8:35 ` Petr Baudis
2008-07-29 0:34 ` Tarmigan
2008-07-29 0:55 ` Junio C Hamano
2008-07-29 1:14 ` Petr Baudis
2008-07-29 1:55 ` Nguyen Thai Ngoc Duy [this message]
2008-07-29 2:02 ` Petr Baudis
2008-07-29 2:12 ` Nguyen Thai Ngoc Duy
2008-07-29 1:05 ` Junio C Hamano
2008-07-29 9:24 ` Jakub Narebski
2008-07-29 11:56 ` git-svn and svn:externals, was " Johannes Schindelin
2008-07-29 12:28 ` Jakub Narebski
2008-07-29 13:04 ` Johannes Schindelin
2008-07-29 16:08 ` Avery Pennarun
2008-07-29 13:08 ` Luciano Rocha
2008-07-29 13:17 ` Johannes Schindelin
2008-08-03 22:48 ` Eric Wong
2008-08-03 23:24 ` Johannes Schindelin
2008-08-03 23:36 ` Eric Wong
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=fcaeb9bf0807281855w3b06f624q18f5ac76a3bb405c@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
/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).