Le vendredi 26 juin 2020 à 07:41 -0700, PGNet Dev a écrit :
> hi,
>
> On 6/25/20 11:58 PM, Nicolas Mailhot wrote:
> > forgemeta works in release mode, with release archives published
> > over
> > http(s). It does not talk at all to source projects using the git
> > protocol (and that is
On 6/26/20 9:35 AM, PGNet Dev wrote:
> that said, _can_ such bash-ism be used in "getting" a forge commit value?
nm, pebkac!
%( git ls-remote %{forgeurl1} | grep HEAD | awk '{print $1}' )
seems to work.
sry 4 the noise.
___
devel mailing list --
while 'exploring' some of the limits of forge syntax/usage, trying to see
if/how bash expansion might work, i find that:
neither
%global forgeurl1 https://github.com/openresty/headers-more-nginx-module
%global commit1 git ls-remote %{forgeurl1} | grep HEAD | awk '{print $1}'
nor
Le vendredi 26 juin 2020 à 07:41 -0700, PGNet Dev a écrit :
> hi,
>
> On 6/25/20 11:58 PM, Nicolas Mailhot wrote:
> > forgemeta works in release mode, with release archives published
> > over
> > http(s). It does not talk at all to source projects using the git
> > protocol (and that is
hi,
On 6/25/20 11:58 PM, Nicolas Mailhot wrote:
> forgemeta works in release mode, with release archives published over
> http(s). It does not talk at all to source projects using the git
> protocol (and that is intentional, since a lot ot things tooling-side
> do not talk the git protocol and
Hi,
forgemeta works in release mode, with release archives published over
http(s). It does not talk at all to source projects using the git
protocol (and that is intentional, since a lot ot things tooling-side
do not talk the git protocol and will never talk the git protocol,
starting with rpm