Hans-Christoph Steiner wrote:
I think the same goes for a merge. That's a lot of email.
which merges are you talking about?
i cannot think of one that will generate "a lot of email" now.
Like merging Pd-extended 0.41.4 and Pd-vanilla 0.42.5
i don't think this is more than a "pretty active
On May 12, 2009, at 12:50 PM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
better stored in soundfiles than in header-files. inappropriate
use should not keep use from having features.
If I import code into the 'sources' tree (for Windows), then all of
that code will be sent to
Hans-Christoph Steiner wrote:
better stored in soundfiles than in header-files. inappropriate use
should not keep use from having features.
If I import code into the 'sources' tree (for Windows), then all of that
code will be sent to pd-cvs.
well, how many packages do you plan to import i
On May 12, 2009, at 5:19 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
The occasional >1meg emails from big commits are kind of a pain,
like when doing an import or merge. It was nice to have immediate
access to scan the diffs for sure. But the web interface to the
diffs
Hans-Christoph Steiner wrote:
The occasional >1meg emails from big commits are kind of a pain, like
when doing an import or merge. It was nice to have immediate access to
scan the diffs for sure. But the web interface to the diffs is a lot
more useful. Ideally, there would be a size cutof
The occasional >1meg emails from big commits are kind of a pain, like
when doing an import or merge. It was nice to have immediate access
to scan the diffs for sure. But the web interface to the diffs is a
lot more useful. Ideally, there would be a size cutoff for the diffs,
like 50k
hi all.
i would really like to have the diffs back in the pd-cvs mails.
as i see it, the current pd-cvs is only useful if you want to track
build-fails of the auto-build machines. it has rather little to do with
repository commits (any more). i would like to get the old behaviour back.
if no
