public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
* gdb-8.3 branch FROZEN
@ 2019-02-27  5:04 Joel Brobecker
  2019-02-27  5:39 ` gdb-8.3-branch now open again (was: "gdb-8.3 branch FROZEN") Joel Brobecker
  0 siblings, 1 reply; 7+ messages in thread
From: Joel Brobecker @ 2019-02-27  5:04 UTC (permalink / raw)
  To: gdb-patches


Hello everyone,

Please avoid pushing any commit to the gdb-8.3-branch branch during
the next few hours. I am working on creating the next pre-release
off this branch.

Also, if at all possible, it saves me a bit of time if you can avoid
pushing changes to the master branch, as it would force me
to handle rebasing and conflict resolution (Eg: ChangeLog).

I will send a followup message when the branch is open again.

Thank you,
-- 
Joel Brobecker

^ permalink raw reply	[flat|nested] 7+ messages in thread

* gdb-8.3-branch now open again (was: "gdb-8.3 branch FROZEN")
  2019-02-27  5:04 gdb-8.3 branch FROZEN Joel Brobecker
@ 2019-02-27  5:39 ` Joel Brobecker
  2019-02-27 16:31   ` gdb-8.3-branch now open again Simon Marchi
  2019-02-27 18:31   ` Sergio Durigan Junior
  0 siblings, 2 replies; 7+ messages in thread
From: Joel Brobecker @ 2019-02-27  5:39 UTC (permalink / raw)
  To: gdb-patches

I have the tarballs, so the gdb-8.3-branch is now open for
changes again.

A small reminder that all Global Maintainers have authority
to approve backporting changes to the branch.

A short annoucement of the pre-release should arrive soon.

Thank you!
-- 
Joel

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gdb-8.3-branch now open again
  2019-02-27  5:39 ` gdb-8.3-branch now open again (was: "gdb-8.3 branch FROZEN") Joel Brobecker
@ 2019-02-27 16:31   ` Simon Marchi
  2019-02-27 18:31   ` Sergio Durigan Junior
  1 sibling, 0 replies; 7+ messages in thread
From: Simon Marchi @ 2019-02-27 16:31 UTC (permalink / raw)
  To: Joel Brobecker; +Cc: gdb-patches

On 2019-02-27 00:39, Joel Brobecker wrote:
> I have the tarballs, so the gdb-8.3-branch is now open for
> changes again.
> 
> A small reminder that all Global Maintainers have authority
> to approve backporting changes to the branch.
> 
> A short annoucement of the pre-release should arrive soon.
> 
> Thank you!

Thanks for your work Joel.  It's now time to push all our dangerous 
patches to master!

Simon

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gdb-8.3-branch now open again
  2019-02-27  5:39 ` gdb-8.3-branch now open again (was: "gdb-8.3 branch FROZEN") Joel Brobecker
  2019-02-27 16:31   ` gdb-8.3-branch now open again Simon Marchi
@ 2019-02-27 18:31   ` Sergio Durigan Junior
  1 sibling, 0 replies; 7+ messages in thread
From: Sergio Durigan Junior @ 2019-02-27 18:31 UTC (permalink / raw)
  To: Joel Brobecker; +Cc: gdb-patches

On Wednesday, February 27 2019, Joel Brobecker wrote:

> I have the tarballs, so the gdb-8.3-branch is now open for
> changes again.
>
> A small reminder that all Global Maintainers have authority
> to approve backporting changes to the branch.
>
> A short annoucement of the pre-release should arrive soon.

Thanks for the release work, Joel.  Always very much appreciated!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* gdb-8.3 branch FROZEN
@ 2019-09-20 21:50 Joel Brobecker
  0 siblings, 0 replies; 7+ messages in thread
From: Joel Brobecker @ 2019-09-20 21:50 UTC (permalink / raw)
  To: gdb-patches


Hello everyone,

Please avoid pushing any commit to the gdb-8.3-branch branch during
the next few hours. I am working on creating the next release
off this branch.

Also, if at all possible, it saves me a bit of time if you can avoid
pushing changes to the master branch, as it would force me
to handle rebasing and conflict resolution (Eg: ChangeLog).

I will send a followup message when the branch is open again.

Thank you,
-- 
Joel Brobecker

^ permalink raw reply	[flat|nested] 7+ messages in thread

* gdb-8.3 branch FROZEN
@ 2019-05-11 18:18 Joel Brobecker
  0 siblings, 0 replies; 7+ messages in thread
From: Joel Brobecker @ 2019-05-11 18:18 UTC (permalink / raw)
  To: gdb-patches


Hello everyone,

Please avoid pushing any commit to the gdb-8.3-branch branch during
the next few hours. I am working on creating the next release
off this branch.

Also, if at all possible, it saves me a bit of time if you can avoid
pushing changes to the master branch, as it would force me
to handle rebasing and conflict resolution (Eg: ChangeLog).

I will send a followup message when the branch is open again.

Thank you,
-- 
Joel Brobecker

^ permalink raw reply	[flat|nested] 7+ messages in thread

* gdb-8.3 branch FROZEN
@ 2019-03-26 22:51 Joel Brobecker
  0 siblings, 0 replies; 7+ messages in thread
From: Joel Brobecker @ 2019-03-26 22:51 UTC (permalink / raw)
  To: gdb-patches


Hello everyone,

Please avoid pushing any commit to the gdb-8.3-branch branch during
the next few hours. I am working on creating the next pre-release
off this branch.

Also, if at all possible, it saves me a bit of time if you can avoid
pushing changes to the master branch, as it would force me
to handle rebasing and conflict resolution (Eg: ChangeLog).

I will send a followup message when the branch is open again.

Thank you,
-- 
Joel Brobecker

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2019-09-20 21:50 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-27  5:04 gdb-8.3 branch FROZEN Joel Brobecker
2019-02-27  5:39 ` gdb-8.3-branch now open again (was: "gdb-8.3 branch FROZEN") Joel Brobecker
2019-02-27 16:31   ` gdb-8.3-branch now open again Simon Marchi
2019-02-27 18:31   ` Sergio Durigan Junior
2019-03-26 22:51 gdb-8.3 branch FROZEN Joel Brobecker
2019-05-11 18:18 Joel Brobecker
2019-09-20 21:50 Joel Brobecker

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).