On 11/21/2018 01:00 AM, Junio C Hamano wrote:
* md/list-lazy-objects-fix (2018-10-29) 1 commit
- list-objects.c: don't segfault for missing cmdline objects
"git rev-list --exclude-promissor-objects" had to take an object
that does not exist locally (and is lazily available) from the
Stefan Beller writes:
>> * sb/submodule-recursive-fetch-gets-the-tip (2018-10-31) 11 commits
>> [...]
>>
>> "git fetch --recurse-submodules" may not fetch the necessary commit
>> that is bound to the superproject, which is getting corrected.
>>
>> Is the discussion on this topic over? What
>
> * sb/submodule-recursive-fetch-gets-the-tip (2018-10-31) 11 commits
> [...]
>
> "git fetch --recurse-submodules" may not fetch the necessary commit
> that is bound to the superproject, which is getting corrected.
>
> Is the discussion on this topic over? What was the outcome?
Please don't
On Sun, Nov 25, 2018 at 11:02:05AM +0900, Junio C Hamano wrote:
> Jeff King writes:
>
> > I do also think in the long run we should be fixing the "unreachable
> > always become loose" issues.
>
> I think I've seen an idea of collecting them into a garbage pack
> floated for at least a few
Jeff King writes:
> I do also think in the long run we should be fixing the "unreachable
> always become loose" issues.
I think I've seen an idea of collecting them into a garbage pack
floated for at least a few times here. What are the downsides? We
no longer will know when these unreachable
On Thu, Nov 22, 2018 at 07:36:54PM +0100, Ævar Arnfjörð Bjarmason wrote:
> > Yeah, my intent had been to circle back around to this, but I just
> > hadn't gotten to it. I'm still pondering a config option or similar,
> > though I remain unconvinced that the cases in which you've showed it
> >
On Sat, Nov 24, 2018 at 11:11:36AM +0900, Junio C Hamano wrote:
> > However, note that the cache-load for finding abbreviations _must_ have
> > the complete list. And has been loading it for some time. So if you run
> > "git-fetch", for example, you've already been running this code for
> >
Jeff King writes:
> Yeah, my intent had been to circle back around to this, but I just
> hadn't gotten to it. I'm still pondering a config option or similar,
> though I remain unconvinced that the cases in which you've showed it
> being slow are actually realistic or worth worrying about (and
On Thu, Nov 22 2018, Jeff King wrote:
> On Wed, Nov 21, 2018 at 11:48:14AM +0100, Ævar Arnfjörð Bjarmason wrote:
>
>>
>> On Wed, Nov 21 2018, Junio C Hamano wrote:
>>
>> > * jk/loose-object-cache (2018-11-13) 9 commits
>> > (merged to 'next' on 2018-11-18 at 276691a21b)
>> > + fetch-pack:
On Wed, Nov 21, 2018 at 11:48:14AM +0100, Ævar Arnfjörð Bjarmason wrote:
>
> On Wed, Nov 21 2018, Junio C Hamano wrote:
>
> > * jk/loose-object-cache (2018-11-13) 9 commits
> > (merged to 'next' on 2018-11-18 at 276691a21b)
> > + fetch-pack: drop custom loose object cache
> > + sha1-file:
On Wed, Nov 21, 2018 at 6:08 PM Stephen P. Smith wrote:
>
> Picking up someones stalled patch is one thing, picking up Linus' patch is in
> a different league.
No, I think it works the other way - my random patches are likely the
_least_ important ones, simply because I can carry them around in
On Thu, Nov 22, 2018 at 11:31 AM Stephen P. Smith wrote:
>
> On Wednesday, November 21, 2018 2:00:16 AM MST Junio C Hamano wrote:
> > [Stalled]
> >
> > * lt/date-human (2018-07-09) 1 commit
> > - Add 'human' date format
> >
> > A new date format "--date=human" that morphs its output depending
>
On Wednesday, November 21, 2018 6:06:13 PM MST Junio C Hamano wrote:
> "Stephen P. Smith" writes:
> > On Wednesday, November 21, 2018 2:00:16 AM MST Junio C Hamano wrote:
> >> [Stalled]
> >>
> >> * lt/date-human (2018-07-09) 1 commit
> >>
> >> - Add 'human' date format
> >>
> >> A new date
"Stephen P. Smith" writes:
> On Wednesday, November 21, 2018 2:00:16 AM MST Junio C Hamano wrote:
>> [Stalled]
>>
>> * lt/date-human (2018-07-09) 1 commit
>> - Add 'human' date format
>>
>> A new date format "--date=human" that morphs its output depending
>> on how far the time is from the
On Wednesday, November 21, 2018 2:00:16 AM MST Junio C Hamano wrote:
> [Stalled]
>
> * lt/date-human (2018-07-09) 1 commit
> - Add 'human' date format
>
> A new date format "--date=human" that morphs its output depending
> on how far the time is from the current time has been introduced.
>
Hi Junio,
On Wed, 21 Nov 2018, Junio C Hamano wrote:
> * js/vsts-ci (2018-10-16) 13 commits
> . travis: fix skipping tagged releases
> . README: add a build badge (status of the Azure Pipelines build)
> . tests: record more stderr with --write-junit-xml in case of failure
> . tests: include
On Wed, Nov 21 2018, Junio C Hamano wrote:
> * jk/loose-object-cache (2018-11-13) 9 commits
> (merged to 'next' on 2018-11-18 at 276691a21b)
> + fetch-pack: drop custom loose object cache
> + sha1-file: use loose object cache for quick existence check
> + object-store: provide helpers for
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
The group of last-minute fixes
18 matches
Mail list logo
