David Faure wrote:
> On Sunday 24 April 2016 13:54:02 Stephen Kelly wrote:
>>
>> Why doesn't v5.21.0 tag the d2e7c78c94e6 commit directly instead?
>
> Don't know.
>
> I just call git tag, then git does its magic.
>
> cat $here/modules.git | while read repo branch; do
> echo $repo
> . $here/version
> tagname=v$version
> versionfile=$here/versions/$repo
> if [ ! -f $versionfile ]; then echo "$versionfile not found"; exit 1;
> fi b=`sed '2q;d' $versionfile`
> echo $b
> checkout=$(findCheckout $repo)
> cd $checkout || exit 2
> echo $PWD
> $cmd git fetch --tags || exit 2
> $cmd git tag -a $tagname $b -m "Create tag for $version" # ignore
> error ("already exists") $cmd git push --tags || exit 5
> done
>
> A previous script (make_rc_tag.sh) tagged rc similarly, in that same
> checkout.
>
> You can see it all in the release-tools.git repo, branch frameworks/5.0
Thanks, I had looked around for it but didn't find it. I can't seem to
access that though.
$ git clone kde:release-tools
Cloning into 'release-tools'...
fatal: remote error: access denied or repository not exported: /release-
tools
> Why is this an actual problem btw?
It just seems like a bug.
Thanks,
Steve.
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
