[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Gitlab Migration
From: |
Lars Ingebrigtsen |
Subject: |
Re: Gitlab Migration |
Date: |
Thu, 26 Aug 2021 21:26:24 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
> It's actually the other way around, at least in some cases. With
> patches that are emailed to me, I can fix some simple issues, such as
> commit log messages or simple typos, myself, before applying.
Indeed. But I expect that whatever we end up with, we (that is, the
Emacs maintainers) won't have to click around, and won't have to
actually merge anything directly. That is, I expect to have a command
in Emacs that says "get that pull request as a patch, apply it, and
don't commit it". So that we can fix stuff up before committing -- as
before.
(I know, I can hear gasps of outrage from git fundamentalists already.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- Re: Gitlab Migration, (continued)
Re: Gitlab Migration, Clément Pit-Claudel, 2021/08/26
Re: Gitlab Migration, Dmitry Gutov, 2021/08/26
Re: Gitlab Migration, Eli Zaretskii, 2021/08/26
Re: Gitlab Migration, Dmitry Gutov, 2021/08/26
Re: Gitlab Migration, Stefan Monnier, 2021/08/26
Re: Gitlab Migration, tomas, 2021/08/27
Structured debbugs list per project (was: Gitlab Migration), Michael Albinus, 2021/08/27
Re: Structured debbugs list per project (was: Gitlab Migration), tomas, 2021/08/27
Re: Structured debbugs list per project, Arthur Miller, 2021/08/27
Re: Structured debbugs list per project, Michael Albinus, 2021/08/28