On 05/18/2017 09:56 PM, Karel Zak wrote:
On Thu, May 18, 2017 at 02:08:49PM -0400, J William Piggott wrote:
On 05/18/2017 06:36 AM, Karel Zak wrote:
8< ---
The important thing on rcN is that we have official tarball, so you
can use it independently on git, add to distros etc.
8< ---
Karel,
I pull from github and haven't seen a new tag since v2.29. Perhaps I
should be pulling from kernel.org, but github should work, no?
I think "git pull" does not always give you all the tags. In doubt I do
explicitly "git fetch --tag remote-name". Maybe "git pull" only pulls
tags if remote-name == origin, I still don't got the full logic.
I push to the both repos in the same time
$ git push; git push github master; git push --tags; git push github --tags
Everything up-to-date
Everything up-to-date
Everything up-to-date
Everything up-to-date
And I see the tags at https://github.com/karelzak/util-linux/tags
Also, it looks like Documentation/source-code-management.txt needs to be
updated. There are no bugfix branches, only tags.
Good point. Updated.
Isn't the KNOWN BUGS:
referring to the v2.13.1 branch as a typo, not the tag?
$ git tag -l | grep v2.13.1
v2.13.1
v2.13.1-REAL
v2.13.1-rc1
v2.13.1-rc2
v2.13.1.1
the first line is unwanted tag... it would be possible to delete it, but I
don't think that remove already published tags is a good idea.
It should not be a problem to delete tags like it's no problem to delete
branches. Only rebasing branches or re-creating conflicting tags could
be annoying or at least confusing.
cu,
Rudi
Karel
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
