On Thu, Jul 25, 2013 at 5:12 AM, Johannes Sixt wrote:
> Am 7/25/2013 10:03, schrieb Eric Sunshine:
>> The tests in this series identify real bugs in dealing with empty
>> ranges, which the subsequent patches fix. The test are possible
>> because one can specify an empty range via blame/log -L, how
Am 7/25/2013 10:03, schrieb Eric Sunshine:
> The tests in this series identify real bugs in dealing with empty
> ranges, which the subsequent patches fix. The test are possible
> because one can specify an empty range via blame/log -L, however, I
> now realize that the ability for -L to create empt
On Thu, Jul 25, 2013 at 4:03 AM, Eric Sunshine wrote:
> I don't
> really consider this a good argument in favor of -Lfoo,+0 representing
> an empty range, and it's a very poor substitute for Michael Haggerty's
> more expressive proposal [1].
>
> [1]:
> http://thread.gmane.org/gmane.comp.version-c
On Tue, Jul 23, 2013 at 10:28 AM, Eric Sunshine wrote:
> While implementing multiple -L support for git-blame, I encountered
> several bugs in range-set and line-log resulting in crashes. This
> series fixes those bugs.
>
> Eric Sunshine (5):
> range-set: fix sort_and_merge_range_set() corner ca
Eric Sunshine writes:
> While implementing multiple -L support for git-blame, I encountered
> several bugs in range-set and line-log resulting in crashes. This
> series fixes those bugs.
Acked-by: Thomas Rast
--
Thomas Rast
trast@{inf,student}.ethz.ch
--
To unsubscribe from this list: send th
While implementing multiple -L support for git-blame, I encountered
several bugs in range-set and line-log resulting in crashes. This
series fixes those bugs.
Eric Sunshine (5):
range-set: fix sort_and_merge_range_set() corner case bug
t4211: demonstrate empty -L range crash
range-set: satis
6 matches
Mail list logo
