Re: [lsp4e-dev] LSP4e document corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [lsp4e-dev] LSP4e document corruption

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Wed, 4 May 2022 19:16:43 +0200
Delivered-to: lsp4e-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/lsp4e-dev/>
List-help: <mailto:lsp4e-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/lsp4e-dev>, <mailto:lsp4e-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/lsp4e-dev>, <mailto:lsp4e-dev-request@eclipse.org?subject=unsubscribe>

On Wednesday, May 4, 2022, Ahmed Hussain via lsp4e-dev <lsp4e-dev@xxxxxxxxxxx> wrote:
> We’re just in the process of brushing up some of our fixes for submission. What’s the preferred way to go about it? Should we first raise GitHub issues and then submit the PRs that address them?

The preferred way would be to submit small and independent PRs in including some test case that reproduces the issue and validates the fix (and prevents from regressions). But if this seems too hard, just submit as you think is best and we'll discuss further on the PRs.

Cheers

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers

Follow-Ups:
- Re: [lsp4e-dev] LSP4e document corruption
  - From: Ahmed Hussain

References:
- [lsp4e-dev] LSP4e document corruption
  - From: Thomas Gibson-Robinson
- Re: [lsp4e-dev] LSP4e document corruption
  - From: Mickael Istria
- Re: [lsp4e-dev] LSP4e document corruption
  - From: Thomas Gibson-Robinson
- Re: [lsp4e-dev] LSP4e document corruption
  - From: Ahmed Hussain

Prev by Date: Re: [lsp4e-dev] LSP4e document corruption
Next by Date: Re: [lsp4e-dev] LSP4e document corruption
Previous by thread: Re: [lsp4e-dev] LSP4e document corruption
Next by thread: Re: [lsp4e-dev] LSP4e document corruption
Index(es):
- Date
- Thread

Breadcrumbs