On Wednesday, 7 March 2018 at 22:28:26 UTC, ketmar wrote:
H. S. Teoh wrote:
I've pestered Brad about it before, but the real trouble is
the Mailman
software. If you feel motivated enough, pestering the
upstream Mailman
authors about it might actually get us closer to fixing this
problem, as
H. S. Teoh wrote:
I've pestered Brad about it before, but the real trouble is the Mailman
software. If you feel motivated enough, pestering the upstream Mailman
authors about it might actually get us closer to fixing this problem, as
it really isn't a problem on Brad's end either. It's not
On Thu, Mar 08, 2018 at 12:10:28AM +0200, ketmar via Digitalmars-d wrote:
> Seb wrote:
>
> > OT: I don't know what you are doing, but you seem to be the only one
> > who always creates new threads when replying. I assume you use nntp?
> > Maybe something wrong with your client?
>
> it was
Seb wrote:
OT: I don't know what you are doing, but you seem to be the only one who
always creates new threads when replying. I assume you use nntp? Maybe
something wrong with your client?
it was already discussed several times: this is the issue with mailing list
processor: it cannot
On Wednesday, 7 March 2018 at 21:03:52 UTC, H. S. Teoh wrote:
On Wed, Mar 07, 2018 at 12:42:52PM -0800, Timothee Cour via
Digitalmars-d wrote:
[...]
On the contrary, I find using merge is easier to understand,
because it shows clearly individual commits within a single PR,
and also a linear
On Wed, Mar 07, 2018 at 12:42:52PM -0800, Timothee Cour via Digitalmars-d wrote:
> There are lots of articles on this topic, eg:
> https://blog.carbonfive.com/2017/08/28/always-squash-and-rebase-your-git-commits/
> (note that squashing down to 1 commit shouldn't be necessary but at
> least
There are lots of articles on this topic, eg:
https://blog.carbonfive.com/2017/08/28/always-squash-and-rebase-your-git-commits/
(note that squashing down to 1 commit shouldn't be necessary but at
least rebasing should be done)
github UI also allows to rebase (instead of merge)
would really
