[prev in list] [next in list] [prev in thread] [next in thread]
List: haskell-cafe
Subject: Re: [Haskell-cafe] Darcs vs Git
From: Mike Meyer <mwm () mired ! org>
Date: 2015-11-16 18:32:39
Message-ID: CAD=7U2A1OtCsBHQ92EKmuYnoJ5yetsMoq96YimMv1z5xVt4btQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Nov 16, 2015 at 12:11 PM Joachim Durchholz <jo@durchholz.org> wrote:
> Am 16.11.2015 um 18:36 schrieb Mike Meyer:
> I haven't seen you argue what purpose a full history might actually
> have, so I still can't say what value you see in the "full history"
> approach, but ah well - sometimes it's hard to verbalize such feelings,
>
Accuracy. Having watched the soviets change their history texts with each
regime, it bothers me to see history changed. If people actually read
and/or otherwise examined these "carefully crafted change logs" on a
regular basis, I might feel otherwise. But I never look at them unless I'm
chasing a bug, and as far as I can tell, nobody else does either. So
spending time editing history is not only mostly wasted effort, it may well
cause problems for the only use. I don't have any actual proof that this is
the case, but I haven't seen any for any other position, either. If you've
got it, I'd certainly be interested in reading it.
> I just hope that you can accept that other people greatly prefer a log
> which has been geared towards better reviewability.
>
Oh, I don't have a problem doing that. But I expect the same courtesy in
return. In particular, If I choose to donate my work to your project,
you'll not ask me to change my clone of your repo to meet your
expectations, but modify the change log as you pull it to meet your
standards. If that's a hoop you insist contributors jump through, that's
cool. I'll stop submitting them. It's not like I lack things to do.
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Mon, Nov 16, 2015 at 12:11 \
PM Joachim Durchholz <<a href="mailto:jo@durchholz.org">jo@durchholz.org</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Am 16.11.2015 um 18:36 schrieb Mike \
Meyer:<br>I haven't seen you argue what purpose a full history might actually<br> \
have, so I still can't say what value you see in the "full history"<br> \
approach, but ah well - sometimes it's hard to verbalize such \
feelings,<br></blockquote><div><br></div><div>Accuracy. Having watched the soviets \
change their history texts with each regime, it bothers me to see history changed. If \
people actually read and/or otherwise examined these "carefully crafted change \
logs" on a regular basis, I might feel otherwise. But I never look at them \
unless I'm chasing a bug, and as far as I can tell, nobody else does either. So \
spending time editing history is not only mostly wasted effort, it may well cause \
problems for the only use. I don't have any actual proof that this is the case, \
but I haven't seen any for any other position, either. If you've got it, \
I'd certainly be interested in reading it.</div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">I just hope that you can accept that other people greatly \
prefer a log<br> which has been geared towards better reviewability. \
<br></blockquote><div><br></div><div>Oh, I don't have a problem doing that. But I \
expect the same courtesy in return. In particular, If I choose to donate my work to \
your project, you'll not ask me to change my clone of your repo to meet your \
expectations, but modify the change log as you pull it to meet your standards. If \
that's a hoop you insist contributors jump through, that's cool. I'll \
stop submitting them. It's not like I lack things to do.</div></div></div>
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic