> Gesendet: Sonntag, 10. Dezember 2023 um 01:18 Uhr
> Von: "andy pugh" <bodge...@gmail.com>
> An: "EMC developers" <emc-developers@lists.sourceforge.net>
> Betreff: [Emc-developers] 2.9.2
...
> I am hoping not to have to hand-build all the debs again, like I did
> for the 2.9.1 release.
>
> Why did I have to do that? Because between me creating the tag and
> pushing it, there was a commit made. Well. maybe my fault, I could
> have done a --dry-run, but that still leaves a window of opportunity
> for a commit to break the process.
Please allow me to fix the double-installation of that one manual page prior to
the release. Once that is fixed i would like to add the installation of all our
.debs as part of the CI - anything placed redundantly in separate packages
should then show up as a conflict.
Concerning the tag and ensuring that you exactly know what you are tagging,
does it help that you can specify the commit that you want to tag?
NAME
git-tag - Create, list, delete or verify a tag object signed with GPG
SYNOPSIS
git tag [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>] [-e]
<tagname> [<commit> | <object>]
git tag -d <tagname>...
git tag [-n[<num>]] -l [--contains <commit>] [--no-contains <commit>]
[--points-at <object>] [--column[=<options>] | --no-column]
[--create-reflog] [--sort=<key>] [--format=<format>]
[--merged <commit>] [--no-merged <commit>] [<pattern>...]
git tag -v [--format=<format>] <tagname>...
Best,
Steffen
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
