public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Peter Weseloh <Peter.Weseloh@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Nov 2009, #03; Sun, 15)
Date: Sun, 15 Nov 2009 16:26:23 -0800	[thread overview]
Message-ID: <7vtywvb9hs.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: loom.20091116T003914-635@post.gmane.org

Peter Weseloh <Peter.Weseloh@gmail•com> writes:

> Does that mean this feature will not make it into 'master' any time soon? 

It does not mean anything about this _feature_, but it does mean this
particular _implementation_ is not likely to.

> Having the ability to do sparse checkouts only of the repo sounds like a
> way out.

There is a big difference between (a) a feature is desirable and (b) a
particular implementation of that feature does things right.

The change in the topic is very intrusive and I am hesitant to merge it
into even 'next'.  Before considering inclusion to 'next', it does not
matter that much if a topic realizes the feature as it advertises, but it
does matter a lot if it breaks things for people who do not need the
feature.  While 'pu' has carried this topic for quite a long time, we
haven't heard much success report from folks like you with the need for
the feature if this implementation worked well for them without breaking
things.

I am not convinced that it won't regress fundamental things for the common
codepaths when "sparse" is not used, and the latest update patch posted to
the list (I do not think I picked it up) seemed very likely to regress
things for the normal codepath.

> Another question: What's the timeline for 1.7.0? I couldn't find anything
> about it neither here nor in the wiki.

When it is ready.  But it is likely that there won't be 1.6.7.

      parent reply	other threads:[~2009-11-16  0:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 10:23 What's cooking in git.git (Nov 2009, #03; Sun, 15) Junio C Hamano
2009-11-15 22:26 ` Daniel Barkalow
2009-11-15 23:32   ` Sverre Rabbelier
2009-11-16  0:30     ` Daniel Barkalow
2009-11-16  0:11   ` Junio C Hamano
2009-11-15 23:40 ` Peter Weseloh
2009-11-16  0:13   ` James Pickens
2009-11-16  0:26   ` Junio C Hamano [this message]

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=7vtywvb9hs.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox$(echo .)com \
    --cc=Peter.Weseloh@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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