Git Tags

Git Tags

[Stefanie Leisestreichler]

Hi.

I have done this (on box A):

git commit -m "Message"
git tag -a 0.9.0
git push origin master

In my local repository, when I run "git tag" it is showing me "0.9.0".

Then I did (on box B)
git clone ssh://user@host:/path/project.git
cd project
git tag

Now git tag is showing nothing.

Why is the tag only available in my local repository?

Also when I try to
git clone --branch 0.9.0 ssh://user@host:/path/project.git
it tells me: fatal:remote branch not found in upstream repository origin

Why is the tag not available in origin?

Thanks,
Stefanie

Re: Git Tags

[Mateusz Loskot]

On Thu, 29 Nov 2018 at 12:50, Stefanie Leisestreichler
<stefanie.leisestreichler@peter-speer.de> wrote:
>
> git tag -a 0.9.0
> git push origin master
>
> In my local repository, when I run "git tag" it is showing me "0.9.0".
>
> Then I did (on box B)
> git clone ssh://user@host:/path/project.git
> cd project
> git tag
>
> Now git tag is showing nothing.
>
> Why is the tag only available in my local repository?

From https://git-scm.com/book/en/v2/Git-Basics-Tagging
"By default, the git push command doesn’t transfer tags to remote servers.
You will have to explicitly push tags to a shared server after you
have created them."

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net

RE: Git Tags

[Randall S. Becker]

On November 29, 2018 6:56, Mateusz Loskot wrote:
> On Thu, 29 Nov 2018 at 12:50, Stefanie Leisestreichler
> <stefanie.leisestreichler@peter-speer.de> wrote:
> >
> > git tag -a 0.9.0
> > git push origin master
> >
> > In my local repository, when I run "git tag" it is showing me "0.9.0".
> >
> > Then I did (on box B)
> > git clone ssh://user@host:/path/project.git cd project git tag
> >
> > Now git tag is showing nothing.
> >
> > Why is the tag only available in my local repository?
> 
> >From https://git-scm.com/book/en/v2/Git-Basics-Tagging
> "By default, the git push command doesn’t transfer tags to remote servers.
> You will have to explicitly push tags to a shared server after you have created
> them."

git push --tags

and

git fetch --tags

to be symmetrical

Cheers,
Randall

-- Brief whoami:
 NonStop developer since approximately 211288444200000000
 UNIX developer since approximately 421664400
-- In my real life, I talk too much.

Re: Git Tags

[Mateusz Loskot]

On Thu, 29 Nov 2018 at 14:40, Randall S. Becker <rsbecker@nexbridge.com> wrote:
> On November 29, 2018 6:56, Mateusz Loskot wrote:
> > On Thu, 29 Nov 2018 at 12:50, Stefanie Leisestreichler <stefanie.leisestreichler@peter-speer.de> wrote:
> > >
> > > git tag -a 0.9.0
> > > git push origin master
> > >
> > > In my local repository, when I run "git tag" it is showing me "0.9.0".
> > >
> > > Then I did (on box B)
> > > git clone ssh://user@host:/path/project.git cd project git tag
> > >
> > > Now git tag is showing nothing.
> > >
> > > Why is the tag only available in my local repository?
> >
> > >From https://git-scm.com/book/en/v2/Git-Basics-Tagging
> > "By default, the git push command doesn’t transfer tags to remote servers.
> > You will have to explicitly push tags to a shared server after you have created
> > them."
>
> git push --tags
>

After my yesterday experience [1], I'd be careful with git push --tags :)

[1] genuine screenshot and link to related thread at
https://twitter.com/mloskot/status/1068072285846859776

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net

Re: Git Tags

[Ævar Arnfjörð Bjarmason]

On Thu, Nov 29 2018, Stefanie Leisestreichler wrote:

> Hi.
>
> I have done this (on box A):
>
> git commit -m "Message"
> git tag -a 0.9.0
> git push origin master
>
> In my local repository, when I run "git tag" it is showing me "0.9.0".
>
> Then I did (on box B)
> git clone ssh://user@host:/path/project.git
> cd project
> git tag
>
> Now git tag is showing nothing.
>
> Why is the tag only available in my local repository?
>
> Also when I try to
> git clone --branch 0.9.0 ssh://user@host:/path/project.git
> it tells me: fatal:remote branch not found in upstream repository origin

Because --branch <name> means get refs/heads/<name>, tags are not
branches. However, because we're apparently quite loose about this in
the clone/fetch code this does give you the tag if it exists, but
probably not in the way you expect.

We interpret the argument as a branch, and will get not only this tag
but "follow" (see --no-tags in git-fetch(1)) the tag as though it were a
branch and give you all tags leading up to that one. This would give you
a single tag:

    git clone --no-tags --branch v2.19.0 --single-branch https://github.com/git/git.git

But this is a more direct way to do it:

    git init git; git -C git fetch --no-tags https://github.com/git/git.git tag v2.19.0

Which'll since you said it failed that's because you haven't pushed the
tag. Try 'git ls-remote <url>' to see if it's there (it's not).

Git tags

[Oliver Beattie]

Hi,

I have noticed that when a new snapshot is released, it is tagged in
the Git repository, and an old tag is typically removed. While I
understand Wireguard is considered experimental, this is quite
frustrating as a user of the project.

Given tags in Git are extremely lightweight, would it be unreasonable
to keep them around?

Cheers,
Oliver

Re: Git tags

[Daniel Kahn Gillmor]

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

On Thu 2017-06-15 18:07:17 -0700, Oliver Beattie wrote:
> I have noticed that when a new snapshot is released, it is tagged in
> the Git repository, and an old tag is typically removed. While I
> understand Wireguard is considered experimental, this is quite
> frustrating as a user of the project.

Huh, i hadn't noticed that older tags had been removed in the canonical
upstream git repo, i agree that's unusual and rather strange.

> Given tags in Git are extremely lightweight, would it be unreasonable
> to keep them around?

The repository where i record debian packaging changes includes a full
copy of the upstream repo (at least as far as what's been packaged) and
that naturally includes the older tags as well:

    https://anonscm.debian.org/git/collab-maint/wireguard.git/refs/tags

You're always welcome to pull the tags from there (the upstream takgs
should all be cryptographically signed by Jason, so you can verify
authenticity even if the network source is different).

regards,

        --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: Git tags

[Jason A. Donenfeld]

Hi Oliver,

On Fri, Jun 16, 2017 at 3:07 AM, Oliver Beattie <oliver@monzo.com> wrote:
> Given tags in Git are extremely lightweight, would it be unreasonable
> to keep them around?

I can keep them around, no problem. I just thought they looked sort of
cluttered, so I removed them, but if it's useful to you, I don't mind
keeping them.

What use case did you have in mind, anyway, for old tags?

Jason

Re: Git tags

[Martin Eskdale Moen]

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Hi Jason
I usually find it useful when I'm provisioning with ansible to be able to
point to a tag and upgrade when I'm ready, so when I provision new nodes
they all have the same version, even if a new version is out.

On Fri, 16 Jun 2017 at 03:44 Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi Oliver,
>
> On Fri, Jun 16, 2017 at 3:07 AM, Oliver Beattie <oliver@monzo.com> wrote:
> > Given tags in Git are extremely lightweight, would it be unreasonable
> > to keep them around?
>
> I can keep them around, no problem. I just thought they looked sort of
> cluttered, so I removed them, but if it's useful to you, I don't mind
> keeping them.
>
> What use case did you have in mind, anyway, for old tags?
>
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #2: Type: text/html, Size: 1436 bytes --]

Re: Git tags

[Jason A. Donenfeld]

On Fri, Jun 16, 2017 at 2:07 PM, Martin Eskdale Moen
<martinmoen@gmail.com> wrote:
> they all have the same version, even if a new version is out.

Never use old snapshots.

Re: Git tags

[Martin Eskdale Moen]

[-- Attachment #1: Type: text/plain, Size: 559 bytes --]

But the problem is that if I have 20 nodes and need to add some more and
there is a breaking change like there was recently with the psk changing to
peers instead of interface I can't always do that change before I need to
add a new node.
Would just be nice if the tags hung around for maybe a year.

On Fri, 16 Jun 2017 at 13:08 Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> On Fri, Jun 16, 2017 at 2:07 PM, Martin Eskdale Moen
> <martinmoen@gmail.com> wrote:
> > they all have the same version, even if a new version is out.
>
> Never use old snapshots.
>

[-- Attachment #2: Type: text/html, Size: 891 bytes --]

Re: Git tags

[Jason A. Donenfeld]

On Fri, Jun 16, 2017 at 2:12 PM, Martin Eskdale Moen
<martinmoen@gmail.com> wrote:
> But the problem is that if I have 20 nodes and need to add some more and
> there is a breaking change like there was recently with the psk changing to
> peers instead of interface I can't always do that change before I need to
> add a new node.

How many times has this affected you? "Once", I assume. Breaking
changes certainly aren't the norm, and I'm sorry that it happened at
all and you have to deal with it. Big hassle. I don't want to subject
folks to that again if I don't have to. It still _may_ happen, but I
hope it won't, and we're working steadily toward the goal of
stabilizing.

> Would just be nice if the tags hung around for maybe a year.

This is currently experimental software. Someday it won't be
experimental, but today it is. You should not use old snapshots,
period. I'd strongly advise you to update all your nodes.

(However, I'll keep old tags around, because Oliver asked, and my only
reason for actually removing the tags was I thought cgit looked
prettier without the clutter, which isn't a good reason for anything.)

Re: Git tags

[Oliver Beattie]

On Thu, Jun 15, 2017 at 7:44 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote=
:
> Hi Oliver,
>
> On Fri, Jun 16, 2017 at 3:07 AM, Oliver Beattie <oliver@monzo.com> wrote:
>> Given tags in Git are extremely lightweight, would it be unreasonable
>> to keep them around?
>
> I can keep them around, no problem. I just thought they looked sort of
> cluttered, so I removed them, but if it's useful to you, I don't mind
> keeping them.

Many thanks, that's really helpful :-)

>
> What use case did you have in mind, anyway, for old tags?

Often the only record I will keep of the version I've built/am running
is the tag name. Of course this means my process is deficient, I just
thought that there was little downside to keeping them around.

>
> Jason
>

Git tags

[Martyn Welch]

Hi Ben,

Could you please pull the git tags from Linus' tree when you pull?

It aids a little in quickly seeing how far a tree on kernel has moved
forward, at the moment the last tag on your tree is "v2.6.26-rc9" [1].

Martyn

[1]
http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/benh/powerpc.git;a=summary

-- 
Martyn Welch MEng MPhil MIET (Principal Software Engineer)   T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd,        |Registered in England and Wales
Tove Valley Business Park, Towcester,      |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB  VAT:GB 927559189

Re: Git tags

[Geoff Levand]

On 12/04/2009 03:27 AM, Martyn Welch wrote:
> Hi Ben,
> 
> Could you please pull the git tags from Linus' tree when you pull?

You'll need to push the tags out to your repo on k.org too...

-Geoff

Git tags

[Yegor Yefremov]

Hi all,

I don't really know where to post this question. Why, if I check out the 
2.6.24.4 kernel (2.6.24.4 tag 
http://git2.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=16c64cac7d9c6a503f49887219c4fe675e7d43d9) 
from the stable git tree, I get "dirty" added to my kernel version after 
compilation? The 2.6.24.4 is stable as far as I understand.
I have already searched for this info and looked through some tutorials 
like http://linux.yyz.us/git-howto.html, but I didn't find any info that 
would answer my question.

Thank you  in advance.

Best regards,
Yegor

Re: Git tags

[Andre Haupt]

On Thu, Apr 03, 2008 at 03:54:55PM +0200, Yegor Yefremov wrote:
> Hi all,
> 
> I don't really know where to post this question. Why, if I check out the 
> 2.6.24.4 kernel (2.6.24.4 tag 
> http://git2.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=16c64cac7d9c6a503f49887219c4fe675e7d43d9) 
> from the stable git tree, I get "dirty" added to my kernel version after 
> compilation? The 2.6.24.4 is stable as far as I understand.
> I have already searched for this info and looked through some tutorials 
> like http://linux.yyz.us/git-howto.html, but I didn't find any info that 
> would answer my question.

Do you have uncommited local changes in your git tree?

Best regards,

Andre

Re: Git tags

[Yegor Yefremov]

Dear Andre,

thank you for your answer. Yes. I have made some changes to the kernel 
sources. Is it really so, that if I make some changes Makefile or some 
other script notices this fact and adds "dirty" to the kernel version 
string?

Best regards,
Yegor

Andre Haupt wrote:
> On Thu, Apr 03, 2008 at 03:54:55PM +0200, Yegor Yefremov wrote:
>   
>> Hi all,
>>
>> I don't really know where to post this question. Why, if I check out the 
>> 2.6.24.4 kernel (2.6.24.4 tag 
>> http://git2.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commit;h=16c64cac7d9c6a503f49887219c4fe675e7d43d9) 
>> from the stable git tree, I get "dirty" added to my kernel version after 
>> compilation? The 2.6.24.4 is stable as far as I understand.
>> I have already searched for this info and looked through some tutorials 
>> like http://linux.yyz.us/git-howto.html, but I didn't find any info that 
>> would answer my question.
>>     
>
> Do you have uncommited local changes in your git tree?
>
> Best regards,
>
> Andre
>
>   

Re: Git tags

[Andre Haupt]

On Thu, Apr 03, 2008 at 04:40:06PM +0200, Yegor Yefremov wrote:
> Dear Andre,
> 
> thank you for your answer. Yes. I have made some changes to the kernel 
> sources. Is it really so, that if I make some changes Makefile or some 
> other script notices this fact and adds "dirty" to the kernel version 
> string?
If you do not commit your changes (i.e. git status shows modified files)
than yes.

Best regards,

Andre

Re: Git tags

[Andre Haupt]

On Thu, Apr 03, 2008 at 04:47:36PM +0200, Andre Haupt wrote:
> On Thu, Apr 03, 2008 at 04:40:06PM +0200, Yegor Yefremov wrote:
> > Dear Andre,
> > 
> > thank you for your answer. Yes. I have made some changes to the kernel 
> > sources. Is it really so, that if I make some changes Makefile or some 
> > other script notices this fact and adds "dirty" to the kernel version 
> > string?
> If you do not commit your changes (i.e. git status shows modified files)
> than yes.
> 
> Best regards,
> 
> Andre

See also http://mail.nl.linux.org/kernelnewbies/2007-08/msg00045.html

I was bitten by this too and Erik Mouw provided a very valuable answer.


Andre

GIT tags

[Iqbal]

Hi, 

I see that the kernel is advanced from 2.6.23-rc8 to 2.6.23. 
When I do a git-tag -l, at the end I can only see 2.6.23-rc4 and not 2.6.23 or any tags between these two.

So, what I understand is "this list doesn't mess up with the tags", the tags are coming from Linus/kernel.org. 
And, there is no hard fast rule that tags are always updated.

Pl. correct me If I my understanding is wrong.

Also,

How can I get the date when I did the last git-pull/git-fetch?
If there are any good pointers on versioning please pass it on.

Thanks, 
Iqbal

Re: GIT tags

[Felipe Balbi]

Hi,

On 10/22/07, Iqbal <iqbal@ti.com> wrote:
>
> Hi,
>
> I see that the kernel is advanced from 2.6.23-rc8 to 2.6.23.
> When I do a git-tag -l, at the end I can only see 2.6.23-rc4 and not 2.6.23 or any tags between these two.
>
> So, what I understand is "this list doesn't mess up with the tags", the tags are coming from Linus/kernel.org.
> And, there is no hard fast rule that tags are always updated.
>

linux-omap has not yet pushed the tags... maybe Tony will do it in the
next push.

> Pl. correct me If I my understanding is wrong.
>
> Also,
>
> How can I get the date when I did the last git-pull/git-fetch?
> If there are any good pointers on versioning please pass it on.
>
> Thanks,
> Iqbal
>
>
>
>
>
>
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>


-- 
Best Regards,

Felipe Balbi
felipebalbi@users.sourceforge.net

Re: GIT tags

[Trilok Soni]

Hi Iqbal,

On 10/22/07, Iqbal <iqbal@ti.com> wrote:
>
> Hi,
>
> I see that the kernel is advanced from 2.6.23-rc8 to 2.6.23.
> When I do a git-tag -l, at the end I can only see 2.6.23-rc4 and not 2.6.23 or any tags between these two.
>
> So, what I understand is "this list doesn't mess up with the tags", the tags are coming from Linus/kernel.org.
> And, there is no hard fast rule that tags are always updated.

True. You need to do "git fetch tags" for upstream. Looks like Tony
had not fetched tags from kernel.org.

>
> Pl. correct me If I my understanding is wrong.
>
> Also,
>
> How can I get the date when I did the last git-pull/git-fetch?

If you are not messing with your master branch then it will also point
you the latest pulled commit and ofcourse date for that commit.

> If there are any good pointers on versioning please pass it on.
>

If you mean the kernel versioning scheme then there are various
discussion threads and lwn.net articles/presentations might help.


-- 
--Trilok Soni

Re: GIT tags

[Tony Lindgren]

* Trilok Soni <soni.trilok@gmail.com> [071022 06:03]:
> Hi Iqbal,
> 
> On 10/22/07, Iqbal <iqbal@ti.com> wrote:
> >
> > Hi,
> >
> > I see that the kernel is advanced from 2.6.23-rc8 to 2.6.23.
> > When I do a git-tag -l, at the end I can only see 2.6.23-rc4 and not 2.6.23 or any tags between these two.
> >
> > So, what I understand is "this list doesn't mess up with the tags", the tags are coming from Linus/kernel.org.
> > And, there is no hard fast rule that tags are always updated.
> 
> True. You need to do "git fetch tags" for upstream. Looks like Tony
> had not fetched tags from kernel.org.
> 
> >
> > Pl. correct me If I my understanding is wrong.
> >
> > Also,
> >
> > How can I get the date when I did the last git-pull/git-fetch?
> 
> If you are not messing with your master branch then it will also point
> you the latest pulled commit and ofcourse date for that commit.
> 
> > If there are any good pointers on versioning please pass it on.
> >
> 
> If you mean the kernel versioning scheme then there are various
> discussion threads and lwn.net articles/presentations might help.

Sorry, sometimes I forget to do git-pull --tags from the mainline tree.
I'll update the tags in linux-omap tree shortly.

Tony