Alternative Re: Creating a FreeType GitLab merge request
Hin-Tak Leung <[email protected]> Sat, 20 Jan 2024 21:21:18 +0000 (UTC)
| Newsgroups | gmane.comp.fonts.freetype.devel |
|---|---|
| Message-ID | <[email protected]> |
Yes, I think I had an fd gitlab account ages ago but after not using it for a while it got disabled and I am having problem re-enabling it again. Anyway, I have never used the fork/pull/merge facility on gitlab with freetype ever, and it has always been the old-fashion way - how git was originally used with the Linux kernel:
You just do your own work in your own local repo, and after playing with your own local branches, merges, tidying up, etc, do:
git format-patch origin/main..
This exports everything between upstream (origin/main) and your current work (.. , short hand for "..HEAD", difference to the current state of your current branch) as a series of plain text patches. Send those as e-mail attachments to the right people, that's all. Or, if they are simple enough, just inline them in a email body.
The old-fashioned usage of git includes using "git send-email" with those patches too, which inline them as a series of e-mails...
On Saturday, 20 January 2024 at 16:36:45 GMT, Alan Coopersmith <[email protected]> wrote:
On 1/19/24 19:25, Alexei Podtelezhnikov wrote:
> Understandably, you cannot edit files in place. You need an account on
> gitlab.freedesktop.org and [fork] FreeType, which has been done 114
> times already.
And because of restrictions implemented last year on the gitlab server
to cut down on spam & abuse, you'll also need to request the ability
to make forks with your new account:
https://gitlab.freedesktop.org/freedesktop/freedesktop/-/wikis/home
--
-Alan Coopersmith- [email protected]
Oracle Solaris Engineering - https://blogs.oracle.com/solaris