Re: [AMBER-Developers] git branches and boost

From: Ross Walker <ross.rosswalker.co.uk>
Date: Thu, 19 Aug 2010 20:59:47 -0700

Hi Scott,

I'm looking into it. The big problem right now is the updates on all the
branches people have made on the server. As you say it gives updates for all
changes. I think we can turn that off for the moment so it only provides
emails for the trunk. I'm not sure how to improve the readability of the
actual messages though. I'd be open to any suggestions anyone has for better
email notification from git.

All the best
Ross

> -----Original Message-----
> From: Scott Brozell [mailto:sbrozell.rci.rutgers.edu]
> Sent: Thursday, August 19, 2010 7:20 PM
> To: AMBER Developers Mailing List
> Subject: Re: [AMBER-Developers] git branches and boost
>
> Hi,
>
> On Thu, Aug 19, 2010 at 11:31:11AM -0400, case wrote:
> > On Thu, Aug 19, 2010, Ben Roberts wrote:
> > >
> > > By the way, do you or anyone else have views on the best way to
> exchange
> > > changes without necessarily committing them to the master branch?
> I've
> > > just uploaded boost-1.38.0 to my local branch, but don't know
> whether
> > > it's best to use the master branch on gitosis as a general-purpose
> > > sandbox for new features...
> >
> > If you need/want to have others examine your changes, but they are
> still
> > experimental, then create a new branch. The gitosis server has
> branches
> > like "pbsa-dev" and "rism-dev" already, which serve as test-beds for
> new
> > development that can be accessed by people in many locations, but
> which are
> > not mature enough to go into the master.
>
> While on the subject of git, can we improve the readability of the
> email notifications ? Itd be better if they were as clear and simple
> as the cvs notifications.
> There are many problems with them; perhaps the most annoying
> is the substantial repetition - it seems that whenever a branch is
> updated we see duplicates of all the previous commits;
> another annoyance is trying to match the comments to the file
> since the message only has a cryptic long git revision number
> near the comment.
>
> thanks,
> scott
>
>
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers


_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Thu Aug 19 2010 - 21:00:04 PDT
Custom Search