[swift-build-dev] [swift-evolution] [Proposal] Applying local git patches

[Valentin Radu]

Hey Tino,

That makes sense, having a forked repo with your own branch works best for situations like you described, significant or multiple changes to the original repo. I wouldn't use arcane patches either for a custom kernel.

However, I recently had to make a very tiny change to a repo, one line of code and it felt wrong to loose the ability to draw from the original upstream because of it.

It was after all, such a minor change that could have been applied after each upstream pull. I know, this could lead to merging conflicts if you support arbitrary versions (x.x +), however, merging your forked repo would lead to the same thing, but remotely (another thing to worry about)

To be honest, I'm not convinced either this would be the best course of action, but it does build upon git, and it does help in certain situations. I'm not sure how often their occurance is tho

- V


Sent from my iPhone

> On 11 Jan 2016, at 01:20, Tino Heth <2th at gmx.de> wrote:
> 
> Hello Valentin,
> 
> setting up a repository with a custom branch is so easy today, I don't think that I personally would use this feature (actually, I'm quite sure for most developers it is easier to fork a repo than to create a patch…).
> 
> That said, the feature wouldn't hurt me (although I would be quite happy if the Kernel for my Raspi would have a proper repo instead of an arcane buildscript that applies a series of patches)
> 
> Best regards,
> Tino