Re: Hackontest ideas?
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Jul 29, 2008, 02:12 UTC
- Message-ID
- <fcaeb9bf0807281912t4df1b5cap8f1ff33138fda25e@mail.gmail.com>
- In-Reply-To
- <20080729020212.GI10151@machine.or.cz>
On 7/29/08, Petr Baudis <pasky@suse.cz> wrote:
Show 24 quoted lines
> On Tue, Jul 29, 2008 at 08:55:32AM +0700, Nguyen Thai Ngoc Duy wrote: > > 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. > > > But I rather liked the elegancy of just narrowing this down to a > particular subtree. Is there really a good reason to generalize this > further?
I think because it's doable and people do need to narrow to more than one subtree sometimes. Also it would solve ".git* in parent directories" problem that is really hard if you strictly do "narrow down to a particular subtree".
-- Duy