From: "Martin Liška" <mliska@suse.cz>
To: Tobias Burnus <tobias@codesourcery.com>, gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: [PATCH][pushed] contrib: run fetch before pushing Daily bump
Date: Thu, 6 Oct 2022 11:13:35 +0200 [thread overview]
Message-ID: <8b8ed7a4-b8ba-aee1-de91-a84e6ffceeaa@suse.cz> (raw)
In-Reply-To: <138b2bba-cb07-c215-2fdc-cef324bb7f21@codesourcery.com>
On 10/5/22 22:09, Tobias Burnus wrote:
> On 05.10.22 20:41, Martin Liška wrote:
>> +++ b/contrib/gcc-changelog/git_update_version.py
>> @@ -127,6 +127,7 @@ def update_current_branch(ref_name):
>> repo.git.add(datestamp_path)
>> if not args.current:
>> repo.index.commit('Daily bump.')
>> + origin.fetch()
>> if args.push:
>> repo.git.push('origin', branch)
>> print('branch is pushed')
>
> Don't you need a 'rebase' in addition?
Well, no, because that would mean the script won't generate a ChangeLog entry for some commits.
> Or alternately – putting 'fetch'
> before 'commit' and then 'merge' would be alternately possible.
Well, the window is pretty small, in between 'git pull' and processing the ChangeLog entries
it should take only a few seconds before a push is done.
Anyway, it failed today again, let me add more robust logging.
Martin
>
> Tobias
>
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
prev parent reply other threads:[~2022-10-06 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 18:41 Martin Liška
2022-10-05 20:09 ` Tobias Burnus
2022-10-06 9:13 ` Martin Liška [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=8b8ed7a4-b8ba-aee1-de91-a84e6ffceeaa@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jwakely.gcc@gmail.com \
--cc=tobias@codesourcery.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).