From: Christian Couder <email@example.com> To: Jeff Hostetler <firstname.lastname@example.org> Cc: Junio C Hamano <email@example.com>, git <firstname.lastname@example.org> Subject: Re: What's cooking in git.git (Jan 2018, #02; Tue, 9) Date: Thu, 18 Jan 2018 09:56:50 +0100 Message-ID: <CAP8UFD0P7kVo2NP4Wq7OaSV4H1+sqHapuzW5AQef+enNS0S5hw@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Wed, Jan 10, 2018 at 11:03 PM, Jeff Hostetler <firstname.lastname@example.org> wrote: > > > On 1/10/2018 2:57 PM, Junio C Hamano wrote: >> >> Jeff Hostetler <email@example.com> writes: >> >>> On 1/9/2018 6:33 PM, Junio C Hamano wrote: >>>> >>>> -------------------------------------------------- >>>> [Cooking] >>>> >>>> >>>> * jh/fsck-promisors (2017-12-08) 10 commits >>> >>> [...] >>> >>>> * jh/partial-clone (2017-12-08) 13 commits >>> >>> [...] >>> >>> Parts 2 and 3 of partial clone have been simmering >>> for a while now. I was wondering if there were any >>> more comments or questions on them. I don't recall >>> any existing issues. >> >> Me neither. I am still not very happy with fetch_object() not returning anything. I wonder what happens when that function is used to fetch from a repo that cannot provide the requested object. Also I think the "extensions.partialclone = <remote>" config option is not very future proof. If people start using partial clone, it is likely that at some point they will need their repo to talk to more than one remote that is partial clone enabled and I don't see how such a config option can scale in this case. >> I do not mind merging them to 'next' during the feature freeze, but >> we won't be merging them to 'master' soon anyway, and I'd like to >> see us concentrate more on finding and fixing regressions on the >> 'master' front for now. > > I didn't want to rush this -- just check to see if there was > any thing that I should focus on while waiting for 2.16 to ship > and settle down. Thanks for already having commented on the patch series I sent to integrate the external odb with the above work, Christian.
next prev parent reply index Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-09 23:33 Junio C Hamano 2018-01-10 7:56 ` Ævar Arnfjörð Bjarmason 2018-01-10 20:02 ` Junio C Hamano 2018-01-10 16:25 ` Jeff Hostetler 2018-01-10 19:57 ` Junio C Hamano 2018-01-10 22:03 ` Jeff Hostetler 2018-01-18 8:56 ` Christian Couder [this message] 2018-01-18 22:31 ` Jonathan Tan
Reply instructions: You may reply publically 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=CAP8UFD0P7kVo2NP4Wq7OaSV4H1+sqHapuzW5AQef+enNS0S5hw@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
firstname.lastname@example.org list mirror (unofficial, one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox