Re: [dev] which versions are dwm patches intended to apply to cleanly?

From: Ben Woolley <tautolog_AT_gmail.com>
Date: Sat, 2 Jul 2016 13:19:45 -0700

Oh, I think I misread/misunderstood your point before. You seem to be talking about patches that would be attached to prior releases only, and not visible in the folder of the latest release. But you want to try an older patch.

In that case, how about a summary index of all patches? It would annotate the latest merged release in the index, linking to the appropriate release folder. Just treat it as a release folder named "latest".

Really, the script that generated the patches from branches could put it all in one folder using the specification described in the other emails. It can just be git branches under the hood.

My main issue with having to search patches only is that it is far easier on a remote headless server to install git than a web browser, or to download the patch on a laptop and and scp it over to the right folder. I want to be able to just use git or just use a web browser because one is server use and one is desktop/laptop use. Definitely want to keep the patch and tarball view of things for package managers, too.

> On Jul 2, 2016, at 10:12 AM, Eric Pruitt <eric.pruitt_AT_gmail.com> wrote:
>
>> On Sat, Jul 02, 2016 at 09:13:05AM -0700, Ben Woolley wrote:
>> For releases, you could expose patches for only the branches ahead of the
>> release, and that might encourage authors to maintain their branches, and
>> patches could automatically be organized by release. A daily run could update
>> the website automatically.
>>
>> That way, releases posted as a tarball will have patches, while revisions
>> requiring git would have branches in git. No new dependencies, and a simple
>> way to organize all patches without needing to mess with dates or revisions.
>> There would only need to be release version and patch name. Each release
>> could have its own folder with release-specific patches.
>
> I don't like this idea because it adds a lot of extra work if I need a
> patch that doesn't apply cleanly to the current release of dwm. Right
> now, I can just navigate to the website, click the patch name and see a
> list of them. Unless I'm missing something, I would have to use Git to
> clone the sites repo, then cd into the repo, run "git branch" to see
> what branches are available, "git checkout $BRANCH", figure out what the
> name of the patch is then apply it. If it turns out $BRANCH doesn't have
> the patch, I have to search some more.
>
> Eric
>
Received on Sat Jul 02 2016 - 22:19:45 CEST