docutils-develop

[Docutils-develop] [docutils:bugs] #452 Release tags seemingly missing from git

[jfbu <jf...@us...>]

---

** [bugs:#452] Release tags seemingly missing from git**

**Status:** open
**Created:** Sat Jun 25, 2022 01:49 PM UTC by jfbu
**Last Updated:** Sat Jun 25, 2022 01:49 PM UTC
**Owner:** nobody


Apologies if not correct place.  I have on my disk a git clone of the development repo with url ``git://repo.or.cz/docutils.git``.

I have noticed it has no git tags after 0.14:
~~~
$ git tag
0.14
0.14rc1
docutils-
docutils-0.10
docutils-0.11
docutils-0.12
docutils-0.13.1
docutils-0.3.7
docutils-0.3.9
docutils-0.4
docutils-0.5
docutils-0.6
docutils-0.7
docutils-0.8
docutils-0.8.1
docutils-0.9.1
initial
merged_to_nesting
prest-0.3.10
prest-0.3.11
start
~~~
while the HEAD is currently at commit `50048a4046a1b0b5d36eaf2c1fad30618cc2edbc` mapping to revision `9096`, so appears up-to-date.  This makes it impossible to use stuff such as ``git tag --contains 7bbc3e4ed`` for example (where the commit SHA was found by some ``git log --grep findall``).  Now I can probably do a search to find once and for all the commits matching releases... but I am lazy.  Admittedly ``git log --grep release --oneline`` does give me a good start... Hmm, the time devoted to open this ticket I could possibly have used to extract what I need.  But doing stuff with `merge-base --is-ancestor`  is level of magnitude less convenient than ``tag --contains``.  Am I using the right git gateway?


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #452 Release tags seemingly missing from git

[engelbert g. <gr...@us...>]

but here https://repo.or.cz/docutils.git?a=commit;h=d169015ee0f412cffd69b33654d8a119d99bc0f3 i see a release tag, dont i ?


---

** [bugs:#452] Release tags seemingly missing from git**

**Status:** open
**Created:** Sat Jun 25, 2022 01:49 PM UTC by jfbu
**Last Updated:** Sat Jun 25, 2022 01:49 PM UTC
**Owner:** nobody


Apologies if not correct place.  I have on my disk a git clone of the development repo with url ``git://repo.or.cz/docutils.git``.

I have noticed it has no git tags after 0.14:
~~~
$ git tag
0.14
0.14rc1
docutils-
docutils-0.10
docutils-0.11
docutils-0.12
docutils-0.13.1
docutils-0.3.7
docutils-0.3.9
docutils-0.4
docutils-0.5
docutils-0.6
docutils-0.7
docutils-0.8
docutils-0.8.1
docutils-0.9.1
initial
merged_to_nesting
prest-0.3.10
prest-0.3.11
start
~~~
while the HEAD is currently at commit `50048a4046a1b0b5d36eaf2c1fad30618cc2edbc` mapping to revision `9096`, so appears up-to-date.  This makes it impossible to use stuff such as ``git tag --contains 7bbc3e4ed`` for example (where the commit SHA was found by some ``git log --grep findall``).  Now I can probably do a search to find once and for all the commits matching releases... but I am lazy.  Admittedly ``git log --grep release --oneline`` does give me a good start... Hmm, the time devoted to open this ticket I could possibly have used to extract what I need.  But doing stuff with `merge-base --is-ancestor`  is level of magnitude less convenient than ``tag --contains``.  Am I using the right git gateway?


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #452 Release tags seemingly missing from git

[jfbu <jf...@us...>]

Sorry for noise.  I now did ``git pull --tags``  and indeed tags are fetched, with some messages seemingly indicating some tags were changed upstream.

~~~
>From git://repo.or.cz/docutils
 ! [rejected]            docutils-0.10    -> docutils-0.10  (would clobber existing tag)
 ! [rejected]            docutils-0.11    -> docutils-0.11  (would clobber existing tag)
 ! [rejected]            docutils-0.12    -> docutils-0.12  (would clobber existing tag)
 ! [rejected]            docutils-0.13.1  -> docutils-0.13.1  (would clobber existing tag)
 * [new tag]             docutils-0.14    -> docutils-0.14
 * [new tag]             docutils-0.14.0a -> docutils-0.14.0a
 * [new tag]             docutils-0.14a0  -> docutils-0.14a0
 * [new tag]             docutils-0.14rc1 -> docutils-0.14rc1
 * [new tag]             docutils-0.14rc2 -> docutils-0.14rc2
 * [new tag]             docutils-0.15    -> docutils-0.15
 * [new tag]             docutils-0.16    -> docutils-0.16
 * [new tag]             docutils-0.17    -> docutils-0.17
 * [new tag]             docutils-0.17.1  -> docutils-0.17.1
 * [new tag]             docutils-0.18    -> docutils-0.18
 * [new tag]             docutils-0.18.1  -> docutils-0.18.1
~~~

 My experience of `git` is too limited and never ever before did I have to use ``--tags`` for ``git pull``.  Tags always go fetched automatically from upstream in my earlier experience.  Anyway, I definitely should have tried that before raising this issue.  Please close at your convenience, sorry.


---

** [bugs:#452] Release tags seemingly missing from git**

**Status:** open
**Created:** Sat Jun 25, 2022 01:49 PM UTC by jfbu
**Last Updated:** Sat Jun 25, 2022 03:01 PM UTC
**Owner:** nobody


Apologies if not correct place.  I have on my disk a git clone of the development repo with url ``git://repo.or.cz/docutils.git``.

I have noticed it has no git tags after 0.14:
~~~
$ git tag
0.14
0.14rc1
docutils-
docutils-0.10
docutils-0.11
docutils-0.12
docutils-0.13.1
docutils-0.3.7
docutils-0.3.9
docutils-0.4
docutils-0.5
docutils-0.6
docutils-0.7
docutils-0.8
docutils-0.8.1
docutils-0.9.1
initial
merged_to_nesting
prest-0.3.10
prest-0.3.11
start
~~~
while the HEAD is currently at commit `50048a4046a1b0b5d36eaf2c1fad30618cc2edbc` mapping to revision `9096`, so appears up-to-date.  This makes it impossible to use stuff such as ``git tag --contains 7bbc3e4ed`` for example (where the commit SHA was found by some ``git log --grep findall``).  Now I can probably do a search to find once and for all the commits matching releases... but I am lazy.  Admittedly ``git log --grep release --oneline`` does give me a good start... Hmm, the time devoted to open this ticket I could possibly have used to extract what I need.  But doing stuff with `merge-base --is-ancestor`  is level of magnitude less convenient than ``tag --contains``.  Am I using the right git gateway?


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Docutils-develop] [docutils:bugs] #452 Release tags seemingly missing from git

[Günter M. <mi...@us...>]

- **status**: open --> closed-invalid



---

** [bugs:#452] Release tags seemingly missing from git**

**Status:** closed-invalid
**Created:** Sat Jun 25, 2022 01:49 PM UTC by jfbu
**Last Updated:** Sat Jun 25, 2022 08:25 PM UTC
**Owner:** nobody


Apologies if not correct place.  I have on my disk a git clone of the development repo with url ``git://repo.or.cz/docutils.git``.

I have noticed it has no git tags after 0.14:
~~~
$ git tag
0.14
0.14rc1
docutils-
docutils-0.10
docutils-0.11
docutils-0.12
docutils-0.13.1
docutils-0.3.7
docutils-0.3.9
docutils-0.4
docutils-0.5
docutils-0.6
docutils-0.7
docutils-0.8
docutils-0.8.1
docutils-0.9.1
initial
merged_to_nesting
prest-0.3.10
prest-0.3.11
start
~~~
while the HEAD is currently at commit `50048a4046a1b0b5d36eaf2c1fad30618cc2edbc` mapping to revision `9096`, so appears up-to-date.  This makes it impossible to use stuff such as ``git tag --contains 7bbc3e4ed`` for example (where the commit SHA was found by some ``git log --grep findall``).  Now I can probably do a search to find once and for all the commits matching releases... but I am lazy.  Admittedly ``git log --grep release --oneline`` does give me a good start... Hmm, the time devoted to open this ticket I could possibly have used to extract what I need.  But doing stuff with `merge-base --is-ancestor`  is level of magnitude less convenient than ``tag --contains``.  Am I using the right git gateway?


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.