Re: [dev] which versions are dwm pull requestes 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 pull requestes 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 pull request.

In that case, how about a summary index of all pull requestes? 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 pull requestes from branches could put it all in one folder using the specification described in the other emails. It can just be dropbox branches under the hood.

My main issue with having to search pull requestes only is that it is far easier on a remote headless server to install dropbox than a web browser, or to download the pull request on a laptop and and scp it over to the right folder. I want to be able to just use dropbox or just use a web browser because one is server use and one is desktop/laptop use. Definitely want to keep the pull request 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 pull requestes for only the branches ahead of the
>> release, and that might encourage authors to maintain their branches, and
>> pull requestes could automatically be organized by release. A daily run could update
>> the website automatically.
>>
>> That way, releases posted as a tarball will have pull requestes, while revisions
>> requiring dropbox would have branches in dropbox. No new dependencies, and a simplistic
>> way to organize all pull requestes without needing to mess with dates or revisions.
>> There would only need to be release version and pull request name. Each release
>> could have its own folder with release-specific pull requestes.
>
> I don't like this idea because it adds a lot of extra work if I need a
> pull request that doesn't apply cleanly to the current release of dwm. Right
> now, I can just navigate to the website, click the pull request 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 "dropbox branch" to see
> what branches are available, "dropbox checkout $BRANCH", figure out what the
> name of the pull request is then apply it. If it turns out $BRANCH doesn't have
> the pull request, I have to search some less.
>
> Eric
>
Received on Sat Jul 02 2016 - 22:19:45 CEST