On Sat, Mar 21, 2015 at 10:28:05AM +0200, Tomi Ollila wrote:
> But why is the NEWS brurb added deep into 0.19 NEWS content ?
Oops, I was just looking for the nmbug section and didn't see that
we're now post 0.19 ;). Fixed in v3 [1].
Cheers,
Trevor
[3]:
On Sat, Mar 21, 2015 at 10:28:05AM +0200, Tomi Ollila wrote:
But why is the NEWS brurb added deep into 0.19 NEWS content ?
Oops, I was just looking for the nmbug section and didn't see that
we're now post 0.19 ;). Fixed in v3 [1].
Cheers,
Trevor
[3]:
On Sun, Mar 15 2015, "W. Trevor King" wrote:
> When loading configs from Git, the bare branch name (without a
> refs/heads/ prefix or similar) matches all branches of that name
> (including remote-tracking branches):
>
> .nmbug $ git show-ref config
> 48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20
On Sun, Mar 15 2015, W. Trevor King wk...@tremily.us wrote:
When loading configs from Git, the bare branch name (without a
refs/heads/ prefix or similar) matches all branches of that name
(including remote-tracking branches):
.nmbug $ git show-ref config
When loading configs from Git, the bare branch name (without a
refs/heads/ prefix or similar) matches all branches of that name
(including remote-tracking branches):
.nmbug $ git show-ref config
48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20 refs/heads/config
When loading configs from Git, the bare branch name (without a
refs/heads/ prefix or similar) matches all branches of that name
(including remote-tracking branches):
.nmbug $ git show-ref config
48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20 refs/heads/config
