public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
* gdb-10 branch FROZEN
@ 2020-10-24  4:22 Joel Brobecker
  2020-10-24  4:46 ` gdb-10-branch now OPEN again (was: "gdb-10 branch FROZEN") Joel Brobecker
  0 siblings, 1 reply; 4+ messages in thread
From: Joel Brobecker @ 2020-10-24  4:22 UTC (permalink / raw)
  To: gdb-patches


Hello everyone,

Please avoid pushing any commit to the gdb-10-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] 4+ messages in thread

* gdb-10-branch now OPEN again (was: "gdb-10 branch FROZEN")
  2020-10-24  4:22 gdb-10 branch FROZEN Joel Brobecker
@ 2020-10-24  4:46 ` Joel Brobecker
  0 siblings, 0 replies; 4+ messages in thread
From: Joel Brobecker @ 2020-10-24  4:46 UTC (permalink / raw)
  To: gdb-patches

Hi everyone,

I have the release tarballs, so the gdb-10-branch is now open again
for patches.

As a small reminder, now that the first official release has been
created, future patches going into the gdb-10-branch need to have
a corresponding PR number. The PR number is used as an anchor to
the correspoding info in bugzilla, so people can quickly get more
information about what fixes were made in the .2.

Thank you!
-- 
Joel

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

* gdb-10 branch FROZEN
@ 2021-04-25  4:03 Joel Brobecker
  0 siblings, 0 replies; 4+ messages in thread
From: Joel Brobecker @ 2021-04-25  4:03 UTC (permalink / raw)
  To: gdb-patches


Hello everyone,

Please avoid pushing any commit to the gdb-10-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] 4+ messages in thread

* gdb-10 branch FROZEN
@ 2020-09-13  2:47 Joel Brobecker
  0 siblings, 0 replies; 4+ messages in thread
From: Joel Brobecker @ 2020-09-13  2:47 UTC (permalink / raw)
  To: gdb-patches


Hello everyone,

Please avoid pushing any commit to the gdb-10-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] 4+ messages in thread

end of thread, other threads:[~2021-04-25  4:03 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-24  4:22 gdb-10 branch FROZEN Joel Brobecker
2020-10-24  4:46 ` gdb-10-branch now OPEN again (was: "gdb-10 branch FROZEN") Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2021-04-25  4:03 gdb-10 branch FROZEN Joel Brobecker
2020-09-13  2:47 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).