Re: clean up commit messages?

[c.]

On 16 Aug 2013, at 03:26, Kai Torben Ohlhus <address@hidden> wrote:

> On 6 August 2013 05:34, c. <address@hidden> wrote:
> 
> [snip]
> 
> Jordi, Kai,
> 
> It would be nice to use this experience to describe clearly a well-defined 
> procedure
> for working on a new feature in a separate clone in a way that makes the 
> final merge
> as painless as possible.
> 
> I'd like to start a wiki page about this if there isn't one already, would 
> you like to help me with it?
> I some text for it could be taken from Kai's blog, how should this page be 
> named?
> 
> There's no hurry though as I'll be away with limited internet access for one 
> week starting tomorrow.
> 
> c.
> 
> 
> Finally I pushed my hopefully conform changesets to the development 
> repository. So far the repository is rebased, thus all my changes are on top. 
> But in the future I start merging again, because rebasing is only possible if 
> the changesets are still drafts.
> 
> I additionally found your new wiki page 
> http://wiki.octave.org/Hg_instructions_for_students c. and added some 
> pictures in the style of the Mercurial manual to get the right ideas quickly. 
> I would like to extend this page by the topic "testing new features" telling 
> you how to pull changesets from students and get rid of them again easily.
> 
> Kai

Hi Kai,

Thanks for you for your pictures and edits to the wiki page but that was not 
complete yet,
please wait until I have completed it an Jordi has reviewed it so we can get 
the procedure
for code "submission" right before you do further edits.

Also that page will need to be moved to a section of 
http://wiki.octave.org/Mercurial so, 
even though it does look cool, I am afraid your sectioning will have to change 
(or at 
least be all increased one level).

I temporaririly commented out your pictures from the page as they look so huge 
on my 
screen they make it difficult for me to follow the contents of the page. When 
done editing 
I'll resize them and put them back in.

Actually the new "submission" procedure, if we get it right, 
should make all that editing and rebasing of all the old changesets 
unneeded.

You are somehow being used as Guinea pig to test and perfect the procedure,
it make take a bit more work but you should be happy to know this is for the 
good of humanity as whole (or at least for the good of future students and 
mentors)

c.