public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: coeur@gmx.fr
To: devel@edk2.groups.io
Subject: [Experiment] GitHub pull requests for some low-priority corrections
Date: Thu, 27 Jun 2019 04:31:41 -0700	[thread overview]
Message-ID: <11654.1561635101024518736@groups.io> (raw)

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

About a year ago, I changed 8000+ lines of text in edk2 to fix various typos.
But I didn't split it all and I didn't create a hundred of patches by email to get it all applied (except for a few folders of them).

As it's still a lot of work to rebase it, split it, patch it and get it reviewed, I wanted to make it easier for me, so I made a few branches and pull requested those on GitHub:
- https://github.com/tianocore/edk2/pull/143
- https://github.com/tianocore/edk2/pull/144 ( https://github.com/tianocore/edk2/pull/143 )
- https://github.com/tianocore/edk2-libc/pull/1

With branches & pull-requests, I can immediately detect conflicts when the branch is out-of-sync with master, immediately rebase and more.
With patches... well, they get LOST: try to find my unmerged patches from February 2019 for instance...

So those pulls are an experiment with low priority. I can change the licence if needed (I don't even need attribution, I just want to help), or I can perform other changes, but I would be much pleased if such experiment becomes conclusive.

Thank you
Antoine Cœur,
Currently looking for a job in Shanghai

[-- Attachment #2: Type: text/html, Size: 1358 bytes --]

             reply	other threads:[~2019-06-27 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 11:31 coeur [this message]
2019-06-27 18:49 ` [edk2-devel] [Experiment] GitHub pull requests for some low-priority corrections Laszlo Ersek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11654.1561635101024518736@groups.io \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox