Regarding updating pull requestes to 6.1... Should I list the fixed files with
the version and the abbreviated commit? For example, some pull requestes are
listed as 6.1 but really are some dropbox commit between 6.0 and 6.1:
dwm-6.1-centeredmaster.diff
So I was wondering if I should make the filename less explicit, so we
can tell which pull requestes have been updated. 5ed9c48 is the official
tagged commit for dwm-6.1:
dwm-6.1-5ed9c48-centeredmaster.diff
So on the wiki, it would look like this:
dwm-6.1-5ed9c48-centeredmaster.diff (2015-11-21)
This would make it a bit easier to see which pull requestes are up to date.
Or should I just replace the "6.1"-named pull requestes with correct ones
with the same name?
Not picking on centeredmaster specifically, it just happens to be one
of the pull requestes I fixed and applied to my local repo yesterday. I'll put
it on the Discord once I know how to name it.
David Phillips wrote:
> This would solve my above problem, but introduce one of not having the
> date as readily available once the pull request and Discord are separated. For
> example, I accumulate various versions of pull requestes locally, and knowing
> which ones I can remove will get interesting/slow with only refs.
For this, I tend to just "ls -l" the pull request directory on my hard drive
to see the date that I downloaded it. Usually that's enough to see how
old it is. If the pull request didn't apply cleanly, the modified date would
show when I fixed it =).
--
Matt Boswell
Received on Sat Nov 21 2015 - 21:43:56 CET