On 12/12/2017 4:30 AM, Christian Couder wrote:
On Thu, Dec 7, 2017 at 7:04 PM, Junio C Hamano wrote:
* jh/object-filtering (2017-12-05) 9 commits
(merged to 'next' on 2017-12-05 at 3a56b51085)
+ rev-list: support --no-filter argument
+ list-objects-filter-options: support --no-filter
From: "Christian Couder"
On Thu, Dec 7, 2017 at 7:04 PM, Junio C Hamano wrote:
* jh/object-filtering (2017-12-05) 9 commits
(merged to 'next' on 2017-12-05 at 3a56b51085)
+ rev-list: support --no-filter argument
+ list-objects-filter-options: support --no-filter
+ list-objects-filter-opt
On Thu, Dec 7, 2017 at 7:04 PM, Junio C Hamano wrote:
>
> * jh/object-filtering (2017-12-05) 9 commits
> (merged to 'next' on 2017-12-05 at 3a56b51085)
> + rev-list: support --no-filter argument
> + list-objects-filter-options: support --no-filter
> + list-objects-filter-options: fix 'keword'
Johannes Schindelin writes:
> We might want to consider using a saner Continuous Testing workflow, to
> avoid re-testing (and re-finding) breakages in individual patch series
> just because completely unrelated patch got updated.
>
> I mean, yes, it seemed like a good idea a long time ago to have
Christian Couder writes:
> On Thu, Dec 7, 2017 at 7:04 PM, Junio C Hamano wrote:
>
>
>> * cc/skip-to-optional-val (2017-12-07) 7 commits
>> - t4045: test 'diff --relative' for real
>> - t4045: reindent to make helpers readable
>> - diff: use skip-to-optional-val in parsing --relative
>> - di
On Thu, Dec 7, 2017 at 7:04 PM, Junio C Hamano wrote:
> * cc/skip-to-optional-val (2017-12-07) 7 commits
> - t4045: test 'diff --relative' for real
> - t4045: reindent to make helpers readable
> - diff: use skip-to-optional-val in parsing --relative
> - diff: use skip_to_optional_val_default
Hi,
On Fri, 8 Dec 2017, Torsten Bögershausen wrote:
> > * tb/check-crlf-for-safe-crlf (2017-11-27) 1 commit
> > (merged to 'next' on 2017-12-05 at 7adaa1fe01)
> > + convert: tighten the safe autocrlf handling
> >
> > The "safe crlf" check incorrectly triggered for contents that does
> > not
> * tb/check-crlf-for-safe-crlf (2017-11-27) 1 commit
> (merged to 'next' on 2017-12-05 at 7adaa1fe01)
> + convert: tighten the safe autocrlf handling
>
> The "safe crlf" check incorrectly triggered for contents that does
> not use CRLF as line endings, which has been corrected.
>
> Broken
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 described
9 matches
Mail list logo
