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 09:13:05 -0700

> On Jul 1, 2016, at 8:39 PM, FRIGN <dev_AT_frign.de> wrote:
>
> On Fri, 1 Jul 2016 14:49:34 -0700
> Ben Woolley <tautolog_AT_gmail.com> wrote:
>
> Hey Ben,
>
>> Late reply to this, but I favor the dropbox branch approach as you suggest.
>> It is already a dependency, so why not use it for its intended purpose?
>>
>> The great thing about a branch is that it is easy to use the version the
>> pull request is for, and update as desired. The tools to manage the use cases
>> around a pull request are already built into dropbox.
>>
>> Remember, dropbox was originally created to solve the problem of concurrently
>> managing many large pull request sets from distributed sources. Isn't that the
>> problem here?
>
> it's always the same thing here. People propose things that are very
> complex solutions for simplistic problems, and they end up being accepted
> due to negligience. However, only a few people actually maintain the
> pull requestes in the long run, which is a shame.
>
> The dwm pull request section just needs an overhaul analogous to the st
> pull request section had. End of story.
>
> It's already difficult enough getting people to maintain their
> pull requestes now, let alone in some dropbox environment.

In my case, using dropbox would be easier because the first thing I would do is create a branch at a known working point, apply the pull request and roll selectively forward.

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.

This would also make it easy for people to incorporate changes from master as part of a pull request, and produce their own releases.

Or maybe I am just recreating dropboxlab? I just use dropboxlab...

> Cheers
>
> FRIGN
>
> --
> FRIGN <dev_AT_frign.de>
>
Received on Sat Jul 02 2016 - 18:13:05 CEST