Hi Junio,
On Sat, 4 Aug 2018, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > On Thu, 2 Aug 2018, Junio C Hamano wrote:
> >
> >> * pk/rebase-in-c (2018-07-30) 3 commits
> >> - builtin/rebase: support running "git rebase "
> >> - rebase: refactor common shell functions into their own
On Tue, 7 Aug 2018 at 16:36, Junio C Hamano wrote:
> Jakub Narebski writes:
>> Junio C Hamano writes:
>>
>>> * ds/commit-graph-with-grafts (2018-07-19) 8 commits
>>> (merged to 'next' on 2018-08-02 at 0ee624e329)
>>> ...
>>> Will merge to 'master'.
>>
>> Derrick wrote that he will be sending
Jakub Narebski writes:
> Junio C Hamano writes:
>
>> * ds/commit-graph-with-grafts (2018-07-19) 8 commits
>> (merged to 'next' on 2018-08-02 at 0ee624e329)
>> ...
>> Will merge to 'master'.
>
> Derrick wrote that he will be sending v2 of this patch series in a few
> weeks, among others to mak
Junio C Hamano writes:
> * 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 with grafts
> + c
Stefan Beller writes:
>> You are the second one who were negatively affected by Stefan's
>> "summary" that reads a lot more in what I said than what actually
>> was said by me. Stop paying attention to that message, but do go to
>> the original if you want to hear what I actually said.
>
> Pleas
Johannes Schindelin writes:
> Hi Junio,
>
> On Thu, 2 Aug 2018, Junio C Hamano wrote:
>
>> * pk/rebase-in-c (2018-07-30) 3 commits
>> - builtin/rebase: support running "git rebase "
>> - rebase: refactor common shell functions into their own file
>> - rebase: start implementing it as a builtin
Hi Junio,
On Thu, 2 Aug 2018, Junio C Hamano wrote:
> * pk/rebase-in-c (2018-07-30) 3 commits
> - builtin/rebase: support running "git rebase "
> - rebase: refactor common shell functions into their own file
> - rebase: start implementing it as a builtin
>
> Rewrite of the "rebase" machinery
Stefan Beller writes:
> - The second part of having an immediate plan is *very* nice
> to see, though I would argue that it could be improved
> by having these updates in the thread instead of summarized
> unrelated to that thread.
>
> We do not do this for now due to tooling issues, I su
On Fri, Aug 3, 2018 at 1:07 PM Junio C Hamano wrote:
>
> Brandon Williams writes:
>
> > [1]
> > https://public-inbox.org/git/cagz79kygs4dvoetygx01cinrxxlcqgxovsplhmgyz8b51lz...@mail.gmail.com/
> > This mail seems to counter that indicating that the "What's Cooking"
> > emails should not be used
Brandon Williams writes:
> [1]
> https://public-inbox.org/git/cagz79kygs4dvoetygx01cinrxxlcqgxovsplhmgyz8b51lz...@mail.gmail.com/
> This mail seems to counter that indicating that the "What's Cooking"
> emails should not be used as a status update.
You are the second one who were negatively aff
On 08/03, Junio C Hamano wrote:
> Junio C Hamano writes:
>
> > "brian m. carlson" writes:
> >
> >> On Fri, Aug 03, 2018 at 11:40:08AM -0700, Junio C Hamano wrote:
> >>> "brian m. carlson" writes:
> >>>
> >>> > On Thu, Aug 02, 2018 at 04:02:36PM -0700, Junio C Hamano wrote:
> >>> >> ---
Junio C Hamano writes:
> "brian m. carlson" writes:
>
>> On Fri, Aug 03, 2018 at 11:40:08AM -0700, Junio C Hamano wrote:
>>> "brian m. carlson" writes:
>>>
>>> > On Thu, Aug 02, 2018 at 04:02:36PM -0700, Junio C Hamano wrote:
>>> >> --
>>> >> [Ne
"brian m. carlson" writes:
> On Fri, Aug 03, 2018 at 11:40:08AM -0700, Junio C Hamano wrote:
>> "brian m. carlson" writes:
>>
>> > On Thu, Aug 02, 2018 at 04:02:36PM -0700, Junio C Hamano wrote:
>> >> --
>> >> [New Topics]
>> >
>> > I had expected
On Fri, Aug 03, 2018 at 11:40:08AM -0700, Junio C Hamano wrote:
> "brian m. carlson" writes:
>
> > On Thu, Aug 02, 2018 at 04:02:36PM -0700, Junio C Hamano wrote:
> >> --
> >> [New Topics]
> >
> > I had expected to see
> > <20180729192803.1047050-1-
"brian m. carlson" writes:
> On Thu, Aug 02, 2018 at 04:02:36PM -0700, Junio C Hamano wrote:
>> --
>> [New Topics]
>
> I had expected to see
> <20180729192803.1047050-1-sand...@crustytoothpaste.net> (the refspec @
> handling) in this list, but I don
On Thu, Aug 02, 2018 at 04:02:36PM -0700, Junio C Hamano wrote:
> --
> [New Topics]
I had expected to see
<20180729192803.1047050-1-sand...@crustytoothpaste.net> (the refspec @
handling) in this list, but I don't. Were you expecting changes or
addit
Pratik Karki writes:
> Hi Junio,
>
> On Fri, Aug 3, 2018 at 4:47 AM Junio C Hamano wrote:
>>
>> * pk/rebase-in-c (2018-07-30) 3 commits
>> - builtin/rebase: support running "git rebase "
>> - rebase: refactor common shell functions into their own file
>> - rebase: start implementing it as a b
Stefan Beller writes:
> On Thu, Aug 2, 2018 at 4:02 PM Junio C Hamano wrote:
>
>> * sb/config-write-fix (2018-08-01) 3 commits
>> - git-config: document accidental multi-line setting in deprecated syntax
>> - config: fix case sensitive subsection names on writing
>> - t1300: document current
Hi Junio,
On Fri, Aug 3, 2018 at 4:47 AM Junio C Hamano wrote:
>
> * pk/rebase-in-c (2018-07-30) 3 commits
> - builtin/rebase: support running "git rebase "
> - rebase: refactor common shell functions into their own file
> - rebase: start implementing it as a builtin
>
> Rewrite of the "rebas
On Thu, Aug 2, 2018 at 4:02 PM Junio C Hamano wrote:
> * sb/config-write-fix (2018-08-01) 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
>
>
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.
Many topics have moved to 'master'
21 matches
Mail list logo