From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-patches@cygwin.com
Subject: Re: newlib-cygwin master shortlog missing cygwin release tags
Date: Tue, 3 Jan 2023 12:32:52 +0900 [thread overview]
Message-ID: <20230103123252.56e90e85c32c270662bbbc6b@nifty.ne.jp> (raw)
In-Reply-To: <a50c2610-3fb0-f1d6-0e89-a7b622f768b3@Shaw.ca>
On Mon, 2 Jan 2023 18:44:10 -0700
Brian Inglis wrote:
> 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?
Recently, some branches other than master are used
for the releases.
-+--------+---------------------> master (cygwin-3.5.0-dev)
\ \
\ \-------------------> cygwin-3_4-branch
\
\------------] cygwin-3_3-branch (cygwin-3_3_6-release etc.)
You can access them by e.g.:
git log origin/cygwin-3_4-branch
git log origin/cygwin-3_3-branch
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2023-01-03 3:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 1:44 Brian Inglis
2023-01-03 3:32 ` Takashi Yano [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=20230103123252.56e90e85c32c270662bbbc6b@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).