From: Ivan Zakharyaschev <imz@altlinux.org> To: ALT Linux Team development discussions <devel@lists.altlinux.org> Subject: Re: [devel] gear inheritance ([#207943] FAILED srpm=0ad-data-0.0.23-alt1.src.rpm 0ad.git=0.0.23-alt1) Date: Thu, 7 Jun 2018 11:07:35 +0300 (MSK) Message-ID: <alpine.LFD.2.20.1806071105240.3504@imap.altlinux.org> (raw) In-Reply-To: <20180607073859.GE20609@imap.altlinux.org> [-- Attachment #1: Type: text/plain, Size: 1504 bytes --] On Thu, 7 Jun 2018, Michael Shigorin wrote: > On Thu, Jun 07, 2018 at 10:19:53AM +0300, Aleksei Nikiforov wrote: > > > In http://git.altlinux.org/gears/0/0ad.git Тут всё-таки речь была о том, что автоматика не сработала, а не о том, как люди деалют git push. Насколько я понимаю. > > > the last tag which is `0.0.22-alt2' was pushed `38 hours ago', > > > but the head `sisyphus` was updated `7 months ago'. > > > In other words, a release tag was pushed without updating a head. > > > Now, was that intentional or deliberate? :-) > > > Lost the game though. > > Ну почему, там была просто пересборка с новым бустом -- > хорошо, конечно, сохранить сведения об этом, но ввиду > малого зазора между сборками я бы уже тащил новую. > > > That's actually a good question how this happened. > > Как at@ и описал, вопрос не в том, как (пушнут только тэг, > но не бранч, коммиты-то потянутся за любой из этих меток) > -- а в том, было ли так задумано. :-) > > Сам сейчас обычно делаю так для ясности: > git push --follow-tags --set-upstream origin master > > > 2018-Jun-06 09:02:49 :: task #207834 for sisyphus started by darktemplar: > > #100 build 0.0.22-alt2 from /people/darktemplar/packages/0ad.git fetched > > at 2018-Jun-05 12:59:00 > > -- > ---- WBR, Michael Shigorin / http://altlinux.org > ------ http://opennet.ru / http://anna-news.info > _______________________________________________ > Devel mailing list > Devel@lists.altlinux.org > https://lists.altlinux.org/mailman/listinfo/devel
next prev parent reply other threads:[~2018-06-07 8:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-07 3:41 Alexey Tourbin 2018-06-07 7:19 ` Aleksei Nikiforov 2018-06-07 7:39 ` Michael Shigorin 2018-06-07 8:07 ` Ivan Zakharyaschev [this message] 2018-06-07 10:05 ` Dmitry V. Levin
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=alpine.LFD.2.20.1806071105240.3504@imap.altlinux.org \ --to=imz@altlinux.org \ --cc=devel@lists.altlinux.org \ /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
ALT Linux Team development discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \ devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru public-inbox-index devel Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git