[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vtk-developers
Subject:    Re: [vtk-developers] Workflow suggestion #1
From:       Bill Lorensen <bill.lorensen () gmail ! com>
Date:       2015-03-31 22:58:53
Message-ID: CADZJ4hPQOzHeEmsN-F4u70-xhBnEQUWTFV2ggiexyX+WBx6Kaw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I'm suggesting that we recommend this. Not automating it.
On Mar 31, 2015 3:47 PM, "Ben Boeckel" <ben.boeckel@kitware.com> wrote:

> On Tue, Mar 31, 2015 at 15:16:56 -0700, Bill Lorensen wrote:
> > I suggest that the title and description for a topic be the commit
> > message and the commit description respectively.
> >
> > Otherwise, the commit message is at least another click away.
>
> Reviewing commit messages is one thing that could definitely be nicer
> with GitLab (and you can't comment on them either). Getting GitLab to do
> it for us would mean patching GitLab, but I might be able to take a
> quick look at it for single-commit branches at least (this is what
> GitHub does). Multi-commit branches will be trickier.
>
> One problem I see right off the bat though would be that the description
> doesn't get edited if the commit message is revised. I doubt that would
> be trivial to get right though :/ .
>
> --Ben
>

[Attachment #5 (text/html)]

<p dir="ltr">I&#39;m suggesting that we recommend this. Not automating it.</p>
<div class="gmail_quote">On Mar 31, 2015 3:47 PM, &quot;Ben Boeckel&quot; &lt;<a \
href="mailto:ben.boeckel@kitware.com">ben.boeckel@kitware.com</a>&gt; wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Mar 31, 2015 at 15:16:56 \
-0700, Bill Lorensen wrote:<br> &gt; I suggest that the title and description for a \
topic be the commit<br> &gt; message and the commit description respectively.<br>
&gt;<br>
&gt; Otherwise, the commit message is at least another click away.<br>
<br>
Reviewing commit messages is one thing that could definitely be nicer<br>
with GitLab (and you can&#39;t comment on them either). Getting GitLab to do<br>
it for us would mean patching GitLab, but I might be able to take a<br>
quick look at it for single-commit branches at least (this is what<br>
GitHub does). Multi-commit branches will be trickier.<br>
<br>
One problem I see right off the bat though would be that the description<br>
doesn&#39;t get edited if the commit message is revised. I doubt that would<br>
be trivial to get right though :/ .<br>
<br>
--Ben<br>
</blockquote></div>



_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Search the list archives at: http://markmail.org/search/?q=vtk-developers

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/vtk-developers



[prev in list] [next in list] [prev in thread] [next in thread]