[Mono-dev] github workflow proposals

[Alan]

For commit messages, how about gnome style ones?

http://live.gnome.org/Git/CommitMessages

We'll end up with messages like this:
http://github.com/mono/moon/commit/feadf070d237c1227ff2709cf1d0131d267118e2:)

Alan.

On Tue, Jul 27, 2010 at 11:16 PM, Mark Probst <mark.probst at gmail.com> wrote:

> On Tue, Jul 27, 2010 at 11:42 PM, Rodrigo Kumpera <kumpera at gmail.com>
> wrote:
> > I have another proposition to make. Can we stop using Changelog files?
> Those
> > can be generated from the commit logs for tarballs and releases without
> > losing anything at all. Commit messages would still have to be at least
> as
> > informative as they currently are.
> > Not having Changelog files resolve 90%+ of our sources of conflicts and
> make
> > the forkqueue much more useful. If we are to move to a DVCS style of
> > development, this will be a big barrier otherwise.
>
> I totally agree with this.  A few days ago I wanted to merge a simple
> commit Sanjoy made, and the fork queue would have been perfect for
> this.  Unfortunately it didn't grok the ChangeLog conflict, so I had
> to pull the change myself, rebase it on master and then push it by
> hand.
>
> I also agree with the one-line summaries and work branches in private
> repositories.
>
> Mark
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20100727/24defd7f/attachment.html