From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: newlib-cygwin master shortlog missing cygwin release tags
Date: Mon, 2 Jan 2023 18:44:10 -0700 [thread overview]
Message-ID: <a50c2610-3fb0-f1d6-0e89-a7b622f768b3@Shaw.ca> (raw)
I am confused looking at master shortlog missing cygwin release tags:
https://sourceware.org/git/?p=newlib-cygwin.git;a=shortlog;h=refs/heads/master
the only cygwin tags shown are cygwin-3.5.0-dev and cygwin-3.4.0 the day before
and nothing else back until 2021-10-28 cygwin-3.4.0-dev and cygwin-3_3_0-release
the day before, whereas the summary page shows more tags and different dates:
tags
2 weeks ago cygwin-3.4.3 Cygwin 3.4.3 release tag
3 weeks ago cygwin-3.4.2 Cygwin 3.4.2 release tag
3 weeks ago cygwin-3.4.1 Cygwin 3.4.1 release tag
4 weeks ago cygwin-3.5.0-dev tag
4 weeks ago cygwin-3.4.0 Cygwin 3.4.0 release tag
5 weeks ago cygwin-3.4.0-dev tag
3 months ago cygwin-3_3_6-release Cygwin 3.3.6 release tag
7 months ago cygwin-3_3_5-release Cygwin 3.3.5 release tag
11 months ago cygwin-3_3_4-release Cygwin 3.3.4 release tag
12 months ago cygwin-3_3_3-release Cygwin 3.3.3 release tag
13 months ago cygwin-3_3_2-release Cygwin 3.3.2 release tag
14 months ago cygwin-3_3_1-release Cygwin 3.3.1 release tag
14 months ago cygwin-3_3_0-release Cygwin 3.3.0 release tag
so what am I not getting?
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next reply other threads:[~2023-01-03 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 1:44 Brian Inglis [this message]
2023-01-03 3:32 ` Takashi Yano
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=a50c2610-3fb0-f1d6-0e89-a7b622f768b3@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-patches@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).