On Thu, Aug 16, 2018 at 1:01 AM Junio C Hamano wrote:
> * bp/checkout-new-branch-optim (2018-07-31) 1 commit
> - checkout: optimize "git checkout -b "
>
> "git checkout -b newbranch [HEAD]" should not have to do as much as
> checking out a commit different from HEAD. An attempt is made to
>
Stefan Beller writes:
>>
>> * sb/config-write-fix (2018-08-08) 3 commits
>> - git-config: document accidental multi-line setting in deprecated syntax
>> - config: fix case sensitive subsection names on writing
>> - t1300: document current behavior of setting options
>>
>> Recent update to
On Thu, Aug 16, 2018 at 6:15 AM Derrick Stolee wrote:
>
> On 8/15/2018 7:01 PM, Junio C Hamano wrote:
> > * ds/commit-graph-with-grafts (2018-07-19) 8 commits
> >(merged to 'next' on 2018-08-02 at 0ee624e329)
> > + commit-graph: close_commit_graph before shallow walk
> > + commit-graph:
On 8/15/2018 7:01 PM, Junio C Hamano wrote:
* ds/commit-graph-with-grafts (2018-07-19) 8 commits
(merged to 'next' on 2018-08-02 at 0ee624e329)
+ commit-graph: close_commit_graph before shallow walk
+ commit-graph: not compatible with uninitialized repo
+ commit-graph: not compatible
>
> * sb/config-write-fix (2018-08-08) 3 commits
> - git-config: document accidental multi-line setting in deprecated syntax
> - config: fix case sensitive subsection names on writing
> - t1300: document current behavior of setting options
>
> Recent update to "git config" broke updating
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.
You can find the changes
6 matches
Mail list logo
