public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: GIT tags
Date: Mon, 22 Oct 2007 17:53:31 -0700	[thread overview]
Message-ID: <20071023005330.GI17318@atomide.com> (raw)
In-Reply-To: <5d5443650710220602j27abd789idbf1b7600ace50b6@mail.gmail.com>

* 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

      reply	other threads:[~2007-10-23  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 11:24 GIT tags Iqbal
2007-10-22 11:35 ` Felipe Balbi
2007-10-22 13:02 ` Trilok Soni
2007-10-23  0:53   ` Tony Lindgren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071023005330.GI17318@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=soni.trilok@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox