[Mono-dev] github workflow proposals

Alan alan.mcgovern at gmail.com
Tue Jul 27 18:52:37 EDT 2010


I always figured that [Tag] was just a simple thing to help you relate a
commit to a very general area. i.e. [corlib] or [debugger] or [wcf]. I don't
think we should, or could, define a whitelist of all usable tags. Hackers in
each area would settle on a couple which would make sense.

Alan.

On Tue, Jul 27, 2010 at 11:47 PM, Marek Habersack
<grendel at twistedcode.net>wrote:

> On Tue, 27 Jul 2010 18:41:46 -0400
> Geoff Norton <gnorton at novell.com> wrote:
>
> >
> > On 2010-07-27, at 6:21 PM, Alan wrote:
> >
> > > For commit messages, how about gnome style ones?
> > >
> > > http://live.gnome.org/Git/CommitMessages
> >
> > This is actually very nice.  My only concern is maintaining the list of
> [Tag]'s.
> My sentiment as well. I think the [Tag] is pretty useless in our case.
>
> marek
> >
> > -g
> >
> > >
> > > 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
> > >
> > > _______________________________________________
> > > 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/5eb099ef/attachment.html 


More information about the Mono-devel-list mailing list