On Thu, May 25, 2017 at 12:22:31PM +0200, Jan Pokorný wrote:
> On 25/05/17 00:28 +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Wed, May 24, 2017 at 05:22:43PM +0200, Jan Pokorný wrote:
> >> On 24/05/17 09:58 -0500, Jorge Gallegos wrote:
> >>> On Wed, May 24, 2017 at 04:19:05PM +0200, Jan Pokorný
On 25/05/17 00:28 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, May 24, 2017 at 05:22:43PM +0200, Jan Pokorný wrote:
>> On 24/05/17 09:58 -0500, Jorge Gallegos wrote:
>>> On Wed, May 24, 2017 at 04:19:05PM +0200, Jan Pokorný wrote:
today, I've accidentally attested there are no stability
On Wed, May 24, 2017 at 05:22:43PM +0200, Jan Pokorný wrote:
> On 24/05/17 09:58 -0500, Jorge Gallegos wrote:
> > On Wed, May 24, 2017 at 04:19:05PM +0200, Jan Pokorný wrote:
> >> today, I've accidentally attested there are no stability guarantees
> >> with the on-demand archives from common git ho
On Wed, May 24, 2017, at 11:22 AM, Jan Pokorný wrote:
> Nope, the point is that nothing has changed in the codebase or, for
> that matter, tags. It must have been GitHub that changed how its
> equivalent of "git archive" behaves.
Yep, that's happened in the past, obviously just happened again,
On 24/05/17 09:58 -0500, Jorge Gallegos wrote:
> On Wed, May 24, 2017 at 04:19:05PM +0200, Jan Pokorný wrote:
>> today, I've accidentally attested there are no stability guarantees
>> with the on-demand archives from common git hosting sites when preparing
>> a new pacemaker update, redownloading "
On Wed, May 24, 2017 at 04:19:05PM +0200, Jan Pokorný wrote:
> Hello,
>
> today, I've accidentally attested there are no stability guarantees
> with the on-demand archives from common git hosting sites when preparing
> a new pacemaker update, redownloading "spectool -s 0 pacemaker.spec"
> of the o
