Lars Schneider writes:
>> On 14 Dec 2017, at 00:00, Junio C Hamano wrote:
>>
>> 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
> On 14 Dec 2017, at 00:00, Junio C Hamano wrote:
>
> 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
On Friday 15 December 2017 02:38 AM, Junio C Hamano wrote:
Junio C Hamano writes:
I think you only sent 3/3 in newer rounds, which made it not to
apply to my tree. If you meant to drop changes in 1/3 and 2/3,
perhaps because they were needless churn, then 3/3 needs to be
On Thursday 14 December 2017 10:50 PM, Junio C Hamano wrote:
Kaartic Sivaraam writes:
It seems my series that fixes an error message in 'git-rebase'[1]
(apart from a little cleanups) is missing. I guess I addressed the
issue that was raised in 3/3 as a v3 for that
Hi Junio,
On Wed, 13 Dec 2017, Junio C Hamano wrote:
> * db/doc-workflows-neuter-the-maintainer (2017-12-08) 1 commit
I hope you do not mean this literally. There is no need to bring family
planning into a technical document.
Ciao,
Dscho
Junio C Hamano wrote:
> Jonathan Nieder writes:
>>> * sb/diff-blobfind (2017-12-12) 1 commit
>>> (merged to 'next' on 2017-12-13 at 9a27a20c5f)
>>> + diffcore: add a filter to find a specific blob
>>>
>>> "git diff" family of commands learned --blobfind= that
>>> allows
Junio C Hamano writes:
> I think you only sent 3/3 in newer rounds, which made it not to
> apply to my tree. If you meant to drop changes in 1/3 and 2/3,
> perhaps because they were needless churn, then 3/3 needs to be
> updated not to depend on the changes these two made.
Jonathan Nieder writes:
>> * sb/diff-blobfind (2017-12-12) 1 commit
>> (merged to 'next' on 2017-12-13 at 9a27a20c5f)
>> + diffcore: add a filter to find a specific blob
>>
>> "git diff" family of commands learned --blobfind= that
>> allows you to limit the output only
Hi,
Junio C Hamano wrote:
> * sb/diff-blobfind (2017-12-12) 1 commit
> (merged to 'next' on 2017-12-13 at 9a27a20c5f)
> + diffcore: add a filter to find a specific blob
>
> "git diff" family of commands learned --blobfind= that
> allows you to limit the output only to a change that involves
On Wed, Dec 13 2017, Junio C. Hamano jotted:
>
> * ab/simplify-perl-makefile (2017-12-11) 1 commit
> (merged to 'next' on 2017-12-13 at 1b791d2503)
> + Makefile: replace perl/Makefile.PL with simple make rules
>
> The build procedure for perl/ part has been greatly simplified by
> weaning
Kaartic Sivaraam writes:
> It seems my series that fixes an error message in 'git-rebase'[1]
> (apart from a little cleanups) is missing. I guess I addressed the
> issue that was raised in 3/3 as a v3 for that patch[2]. Are any more
> changes needed?
>
> [1]:
It seems my series that fixes an error message in 'git-rebase'[1]
(apart from a little cleanups) is missing. I guess I addressed the
issue that was raised in 3/3 as a v3 for that patch[2]. Are any more
changes needed?
[1]: <20171127172104.5796-1-kaartic.sivar...@gmail.com>
[2]:
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
13 matches
Mail list logo