[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "If you're still seeing problems, please reopen." [Was: bug#25148:]

From: João Távora
Subject: Re: "If you're still seeing problems, please reopen." [Was: bug#25148:]
Date: Wed, 20 Nov 2019 20:12:28 +0000

On Wed, Nov 20, 2019 at 8:02 PM Eli Zaretskii <address@hidden> wrote:
> > From: João Távora <address@hidden>
> > Date: Wed, 20 Nov 2019 19:29:58 +0000
> > Cc: Lars Ingebrigtsen <address@hidden>, Óscar Fuentes <address@hidden>,
> >       emacs-devel <address@hidden>, Richard Stallman <address@hidden>, 
> > Dmitry Gutov <address@hidden>
> >
> > > AFAIU, you described the wokflow of a developer, not of a
> > > contributor.  I was rather talking about the latter, and mainly before
> > > their PR is accepted and merged.
> >
> > Well, yeah, but from the contributor's side the process is very
> > similar. Apart from not being able actually merge the PR
> > to master, he changes the PR's branch in the very same
> > ways as I (the developer) described in my previous email.
> That branch _is_ the problem.  You don't want that to be a branch in
> our upstream repository.

Why don't you?

(with apologies if you already answered elsewhere)

It's a reasonably "cheap" thing to manipulate in Git and can
be (if we want) ephemeral. (iow even if we accept it we
don't have to integrate it with a merge commit).

As an Emacs developer, I create branches under scratch/
very frequently.  I've now started creating them under the
/scratch/joaot prefix.  The GitLab workflow could be similar
but every user could create branches in his fork of Emacs,
within the emba instance.

Thank you,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]