<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Sep 4, 2014 at 9:12 AM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Thu, 4 Sep 2014, Tobin Isaac wrote:<br>
<br>
><br>
> > My personal opinion is that maintaining a catalog of undesirable commits<br>
> > and detection/enforcement logic is not the best use of maintainer time<br>
> > and will not result in a more efficient system. But if you want to<br>
> > spend your time on it, give it a shot and maybe others will use it too.<br>
><br>
> Funny you should say that.<br>
><br>
> <a href="https://bitbucket.org/petsc/petsc/commits/a04f2a265ee1457256d59a436256ddce6a927374" target="_blank">https://bitbucket.org/petsc/petsc/commits/a04f2a265ee1457256d59a436256ddce6a927374</a><br>
> <a href="https://bitbucket.org/petsc/petsc/commits/7a9516f4bcf47790ec9d70380d83bb015f0d3e8e" target="_blank">https://bitbucket.org/petsc/petsc/commits/7a9516f4bcf47790ec9d70380d83bb015f0d3e8e</a><br>
><br>
> My idea here is (a) create a dotfile in a commit that only gets merged<br>
> into next, and (b) add a hook to 'make info' that warns you if that<br>
> file is present and your branch isn't named 'next'. This change<br>
> doesn't help a maintainer, who knows the workflow and can spot<br>
> undesirable commits better than a script, but it does reach out to<br>
> developers who, ehm, may not have read the wiki, and warns them as<br>
> soon as they start to test their changes on a branch that was based on<br>
> 'next'.<br>
<br>
</div></div>the nightly builds are done in 'detached' mode - so this warning wil always<br>
printed for these builds.<br>
<br>
And when folks hardly look at git messages - I don't thinks they will notice<br>
this message burried in middle of a build. [And most of the time merge/push<br>
is done without a build]. So I don't think this change helps much..<br></blockquote><div><br></div><div>I will notice.</div><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Id rather folks use 'git log ..branch' before 'git merge branch'<br>
<span class="HOEnZb"><font color="#888888"><br>
Satish<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener
</div></div>