Re: Gitlab Migration

[Alan Third]

On Sat, Aug 28, 2021 at 10:05:50AM +0200, Theodor Thornhill wrote:
> 
> 
> On 28 August 2021 09:55:18 CEST, Eli Zaretskii <eliz@gnu.org> wrote:
> >> From: Theodor Thornhill <theo@thornhill.no>
> >> Cc: emacs-devel@gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca,
> >>  danflscr@gmail.com, philipk@posteo.net, sir@cmpwn.com
> >> Date: Fri, 27 Aug 2021 23:04:55 +0200
> >> 
> >> ** Submitting patches by email.
> >> It is possible to send patches using a web interface.  It works by using
> >> the `prepare a patchset` button on your own clone.  So the process
> >> is usually:
> >>   - clone the repo
> >>   - pull it locally
> >>   - do the work
> >>   - push the work
> >>   - use the `prepare a patchset` button or `git format-patch`
> >
> >Does it mean simply sending a patch via email is not supported?  E.g.,
> >I could easily create a patch without a separate clone of the
> >repository, using just the single clone I have already.  You seem to
> >describe something much more complicated, which starts with a separate
> >clone?
> >
> 
> No need for a clone. Mailing a patch is enough. For the web UI thing though I 
> think you need one.

Out of interest, we currently work by attaching patches to emails but
I understand the usual "git" way of doing it is by sending the patch
directly AS an email. Is that something we'd have to do differently?

-- 
Alan Third