unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [Next browser] Common Lisp: mgl-pax: Package SWANK-BACKEND does not exist.
Date: Tue, 11 Sep 2018 17:17:09 -0400	[thread overview]
Message-ID: <20180911211709.GA3238@jasmine.lan> (raw)
In-Reply-To: <87worr4uln.fsf@ambrevar.xyz>

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

On Tue, Sep 11, 2018 at 11:01:08PM +0200, Pierre Neidhardt wrote:
> By the way, I could not rebase+push, upstream complains that I cannot push
> non-fast-forward commits and that I should pull first.  How am I supposed to
> rebase my branch?

For wip-* branches [0], please delete the branch remotely and then push
it again. This is effectively the same thing as force-pushing, but with
an extra step ;) We disabled all forced pushes in our repo on Savannah.

For example:

$ git push origin :branch && git push origin branch

[0] We use the 'wip-' prefix to indicate that history may be rewritten.
Other branches should use merges instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-09-11 21:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 16:24 [Next browser] Common Lisp: mgl-pax: Package SWANK-BACKEND does not exist Pierre Neidhardt
2018-08-24 10:32 ` Pierre Neidhardt
2018-08-24 12:56 ` Ludovic Courtès
2018-08-24 13:15   ` Pierre Neidhardt
2018-08-27  7:24   ` Andy Patterson
2018-08-27  7:42     ` Pierre Neidhardt
2018-08-28  7:36       ` Andy Patterson
2018-08-28 19:18         ` Pierre Neidhardt
2018-08-29  6:18           ` Andy Patterson
2018-09-02 16:59             ` Pierre Neidhardt
2018-09-08 21:49               ` Andy Patterson
2018-09-11 21:01                 ` Pierre Neidhardt
2018-09-11 21:17                   ` Leo Famulari [this message]
2018-09-12  8:10                     ` Pierre Neidhardt

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180911211709.GA3238@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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 public inbox

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

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