On Wednesday 27 April 2016 09:45:42 Stephen Kelly wrote:
> David Faure wrote:
>
> > 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
David Faure wrote:
> 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 $tagnam
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
v
If you look in gitk at karchive (or any other repo), you can see that commit
d2e7c78c94e6 is tagged with both v5.21.0-rc2 and v5.21.0.
If you click on the v5.21.0-rc2 tag, you can see that it tags the commit.
That is the usual thing to do.
Tag: v5.21.0-rc2
object d2e7c78c94e629a60bcff7b5c1abaf
