[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Skipping unexec via a big .elc file
From: |
Yuri Khan |
Subject: |
Re: Skipping unexec via a big .elc file |
Date: |
Wed, 14 Dec 2016 19:06:30 +0700 |
On Wed, Dec 14, 2016 at 5:58 PM, Phil Sainty <address@hidden> wrote:
> If you *really really* want to push a revised history -- bearing
> in mind that it will cause merge issues for anyone who has already
> pulled from that branch (which is why you would usually refrain
> from doing such a thing, and why server-side protection like this
> exists in the first place) -- then you can generally work around
> the protection by deleting the upstream branch and then pushing
> your new version of it.
Scratch branches are personal and others should exercise caution
if/when pulling them. It is okay for the branch owner to delete and
recreate it.
- Re: Skipping unexec via a big .elc file, (continued)
- Re: Skipping unexec via a big .elc file, Richard Stallman, 2016/12/11
- Re: Skipping unexec via a big .elc file, Ken Brown, 2016/12/13
- Re: Skipping unexec via a big .elc file, Ken Raeburn, 2016/12/14
- Re: Skipping unexec via a big .elc file, Lars Ingebrigtsen, 2016/12/14
- Re: Skipping unexec via a big .elc file, Ken Raeburn, 2016/12/15
- Re: Skipping unexec via a big .elc file, Ken Raeburn, 2016/12/15
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2016/12/15
- Re: Skipping unexec via a big .elc file, Clément Pit--Claudel, 2016/12/15
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2016/12/16
- Re: Skipping unexec via a big .elc file, Clément Pit--Claudel, 2016/12/16
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2016/12/16
- Re: Skipping unexec via a big .elc file, Clément Pit--Claudel, 2016/12/16
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2016/12/16