[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] gnu: bash-completion: Update to 2.3.
From: |
Leo Famulari |
Subject: |
Re: [PATCH] gnu: bash-completion: Update to 2.3. |
Date: |
Sat, 6 Aug 2016 23:06:05 -0400 |
User-agent: |
Mutt/1.6.0 (2016-04-01) |
On Fri, Aug 05, 2016 at 08:53:46PM +0200, Andreas Enge wrote:
> The autoreconf phase is strange. Why is it suddenly needed? If there is no
> way around it, you should at least add a comment.
I notice that when projects move to GitHub, they sometimes forget to cut
a new release. GitHub automatically generates a tarball of the source
tree for each tag, and those are not bootstrapped. That's probably what
happened here, and it's worth an upstream bug report, IMO.
- [PATCH] gnu: bash-completion: Update to 2.3., Tomáš Čech, 2016/08/03
- Re: [PATCH] gnu: bash-completion: Update to 2.3., Andreas Enge, 2016/08/05
- Re: [PATCH] gnu: bash-completion: Update to 2.3.,
Leo Famulari <=
- Re: [PATCH] gnu: bash-completion: Update to 2.3., Tomáš Čech, 2016/08/07
- [PATCHv2 1/2] gnu: bash-completion: Modify to modify-phases., Tomáš Čech, 2016/08/07
- [PATCHv2 2/2] gnu: bash-completion: Update to 2.3. Update the patch., Tomáš Čech, 2016/08/07
- Re: [PATCHv2 2/2] gnu: bash-completion: Update to 2.3. Update the patch., Leo Famulari, 2016/08/08
- Re: [PATCHv2 2/2] gnu: bash-completion: Update to 2.3. Update the patch., Tomáš Čech, 2016/08/09
- Re: [PATCHv2 1/2] gnu: bash-completion: Modify to modify-phases., Leo Famulari, 2016/08/08