all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 64369@debbugs.gnu.org
Subject: [bug#64369] Request for merging "mesa-updates" branch
Date: Thu, 20 Jul 2023 19:24:01 +0000	[thread overview]
Message-ID: <87fs5iz8s2.fsf@protonmail.com> (raw)
In-Reply-To: <87wmyuwm1q.fsf@cbaines.net>

On Thu, Jul 20, 2023 at 06:04 PM, Christopher Baines wrote:

>
> John Kehayias <john.kehayias@protonmail.com> writes:
>
>> Are we able to rebase and then force push on savannah? I thought not,
>> or is that just for the master branch? If I can force push (I suppose
>> I could just try later), I would leave off 64738 (zstd in mesa) and
>> rebase on master. Otherwise I guess revert and merge master to
>> mesa-updates.
>
> Not directly, but you can delete the branch and then just push as if it
> is a new branch to effectively force push.
>

Gotcha. That's what I did to rebase on master as of now. Let's see
what happens with the build and go from there.

Thanks!





  reply	other threads:[~2023-07-20 19:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 15:53 bug#64369: Request for merging "mesa-updates" branch John Kehayias via Bug reports for GNU Guix
2023-07-01 10:36 ` [bug#64369] " Christopher Baines
2023-07-05 20:04   ` John Kehayias via Guix-patches via
2023-07-20 15:54 ` John Kehayias via Guix-patches via
2023-07-20 16:03   ` Christopher Baines
2023-07-20 16:23     ` John Kehayias via Guix-patches via
2023-07-20 17:04       ` Christopher Baines
2023-07-20 19:24         ` John Kehayias via Guix-patches via [this message]
2023-07-24 15:14           ` John Kehayias via Guix-patches via
2023-07-28 15:29             ` John Kehayias via Guix-patches via
2023-07-31 15:24               ` bug#64369: " John Kehayias via Guix-patches via

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=87fs5iz8s2.fsf@protonmail.com \
    --to=guix-patches@gnu.org \
    --cc=64369@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=mail@cbaines.net \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.