On 26/09/19 08:44PM, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 24 Sep 2019, Pratyush Yadav wrote:
>
> > On 23/09/19 09:35PM, Johannes Schindelin wrote:
> > > Hi,
> > >
> > > On Wed, 18 Sep 2019, Junio C Hamano wrote:
> > >
> > > > We have a new maintainer for git-gui now. Thanks Pratyush for
Hi,
On Tue, 24 Sep 2019, Pratyush Yadav wrote:
> On 23/09/19 09:35PM, Johannes Schindelin wrote:
> > Hi,
> >
> > On Wed, 18 Sep 2019, Junio C Hamano wrote:
> >
> > > We have a new maintainer for git-gui now. Thanks Pratyush for
> > > volunteering.
> >
> > Excellent!
> >
> > I opened PRs at https
On 23/09/19 09:35PM, Johannes Schindelin wrote:
> Hi,
>
> On Wed, 18 Sep 2019, Junio C Hamano wrote:
>
> > We have a new maintainer for git-gui now. Thanks Pratyush for
> > volunteering.
>
> Excellent!
>
> I opened PRs at https://github.com/prati0100/git-gui/pulls. Pratyush, do
> you accept co
Hi,
On Wed, 18 Sep 2019, Junio C Hamano wrote:
> We have a new maintainer for git-gui now. Thanks Pratyush for
> volunteering.
Excellent!
I opened PRs at https://github.com/prati0100/git-gui/pulls. Pratyush, do
you accept contributions in this form, or should I do anything
differently?
Ciao,
Taylor Blau writes:
> commit-graph files on all repositories hosted on GitHub, and some
> corrupt repositories triggered the behavior.
> ...
> We've been running this patch since a few days before I submitted it to
> ...
> This one has a similar origin story, and has also been running at GitHub
>
On Wed, Sep 18, 2019 at 03:33:15PM -0700, Junio C Hamano wrote:
> * tb/commit-graph-harden (2019-09-09) 3 commits
> - commit-graph.c: handle corrupt/missing trees
> - commit-graph.c: handle commit parsing errors
> - t/t5318: introduce failing 'git commit-graph write' tests
>
> The code to parse
Thomas Gummerer writes:
> I have sent an updated version of this, that integrates the changes
> the js/builtin-add-i topic needs in [*1*]. I think it would be ok to
> pick up that version and keep js/builtin-add-i out of pu until it's
> rebased on top of that.
Thanks, will replace after looking
Martin Ågren writes:
> Hi Junio,
>
> On Thu, 19 Sep 2019 at 01:44, Junio C Hamano wrote:
>
>> * ma/asciidoctor-refmiscinfo (2019-09-16) 3 commits
>> - doc-diff: replace --cut-header-footer with --cut-footer
>> - asciidoctor-extensions: provide ``
>> - Doc/Makefile: give mansource/-version/-ma
Jonathan Tan writes:
>> * jt/cache-tree-avoid-lazy-fetch-during-merge (2019-09-09) 1 commit
>> - cache-tree: do not lazy-fetch tentative tree
>>
>> The cache-tree code has been taught to be less aggressive in
>> attempting to see if a tree object it computed already exists in
>> the reposito
On 09/18, Junio C Hamano wrote:
> * tg/stash-refresh-index (2019-09-05) 3 commits
> - stash: make sure to write refreshed cache
> - merge: use refresh_and_write_cache
> - factor out refresh_and_write_cache function
>
> "git stash" learned to write refreshed index back to disk.
>
> Needs coor
Hi Junio,
On Thu, 19 Sep 2019 at 01:44, Junio C Hamano wrote:
> * ma/asciidoctor-refmiscinfo (2019-09-16) 3 commits
> - doc-diff: replace --cut-header-footer with --cut-footer
> - asciidoctor-extensions: provide ``
> - Doc/Makefile: give mansource/-version/-manual attributes
>
> Update suppo
> * jt/cache-tree-avoid-lazy-fetch-during-merge (2019-09-09) 1 commit
> - cache-tree: do not lazy-fetch tentative tree
>
> The cache-tree code has been taught to be less aggressive in
> attempting to see if a tree object it computed already exists in
> the repository.
>
> Waiting for a respo
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.
We have a new maintainer for git-g
13 matches
Mail list logo
