On Friday 05 November 2010 16:13:20 Jason A. Kates wrote:
> Since you have separated your git repo the commit log on the source
> forge git repo have dried out and really don't reflect daily changes.

Can you be a bit more specific about what the commit log on Source Forge is?  
If it is the stuff they print on the main page about Bacula activity, I think 
that is not really a commit log, but rather a summary of the changes that 
happen at Source Forge.

When we push stuff to the Bacula Source Forge repo, it can have a single 
commit in that push or sometimes hundreds of commits.  It all depends on how 
often we push, and how developers work.  With git, unlike SVN, when you 
commit, it goes into your local repository.  Only when you push do those 
commits get put into the external repo.  This means that unlike SVN, the main 
repo does not show instantaneously the changes the developers are making.  In 
addition, unlike we worked with SVN, now, much development work is done in a 
branch sometimes for months, before it is pushed in the repo -- it all 
depends on how the developer works.  I tend to push little things quickly, 
others tend to wait and accumulate a number of things.

As I say, if you want to see what activity has taken place, you need to do 
a "git pull" "git log"  or a "git pull" and a "gitk".

This is the difference with SVN (a single central repo) and git (multiple 
distributed repos) and isn't something that splitting the Branches caused.

>
> I have set my self up with an account on, www.baculasystems.com  in the
> hopes that I could see the git log (hooking your git log into a rss feed
> would be really nice, think of it as a teaser for people to see what
> they would get if they paid for support)..

You don't need that to see the log.

>
> I haven't be able to yet convince work to pay for support (as they think
> that I just need tar for backups) thus I don't have access to the full
> git repo.

Yes not everyone wants to pay, but that is OK, it is part of what Open Source 
is about.

Kern

>
>                               -Jason
>
> On Fri, 2010-11-05 at 15:39 +0100, Kern Sibbald wrote:
> > Hello Jason,
> >
> > On Friday 05 November 2010 14:53:09 Jason A. Kates wrote:
> > > Jon,
> > > I don't think that your comments are appropriate (why the personal
> > > attack).   BTW every time you test or do a restore it proves a list
> > > more than just faith, your data returns.   This isn't a religion it's
> > > backup software that works incredibly well.   I hope that that we can
> > > keep this list at a more professional level without the personal
> > > attacks.
> > >
> > > With the fork I really do miss being able to read the svn (now git)
> > > commit logs even if I don't have access to the actual commit.   I hope
> > > that Kern or others place the commit logs some place where we all can
> > > access.
> >
> > You do have access to the actual commits.
> >
> > Everything we do for the community is committed to the Source Forge git
> > repo. It took us a few months when creating the Bacula Systems branches
> > to get everything worked out right, pushing to the Source Forge
> > repository was not always timely, but everything is there and can easily
> > be cloned.
> >
> > The two main branches are Branch-5.0, which is the Community production
> > branch, and contains Bacula 5.0.3 plus all the bug fixes that we have
> > made since the 5.0.3 release.  Branch-5.1 contains the latest Community
> > development code.
> >
> > When we make a Bacula release, we always update the ChangeLog file, in
> > between releases, you can always see the latest changes using "git log"
> > or if you want to see it more visually use "gitk".
> >
> > Other than a period of getting our various branches all sorted out,
> > everything is exactly as it has been for the last 8 year (since public
> > release).  Of course, we have move from CVS to SVN, and now to git along
> > the way ...
> >
> > Best regards,
> >
> > Kern
> >
> > >                           -Jason
> > >
> > > On Fri, 2010-11-05 at 09:26 -0400, jon pounder wrote:
> > > > On 11/05/2010 09:08 AM, Heitor Medrado de Faria wrote:
> > > > > Guys,
> > > > >
> > > > > Each new Bacula Enterprise feature, like the: New GUI Configurator,
> > > > > makes me feel that Bacula project will die.
> > > > > It's very frustrating that a project that become a huge success
> > > > > being a free software, is being destroyed like that.
> > > > > I acknowledge that Kern and other developers had lots of
> > > > > development work on Bacula - and there is not huge contribution.
> > > > > But creating a paid fork is not the way of get compensation.
> > > > >
> > > > > Regards,
> > > >
> > > > Don't even say things like this on the list, haven't you figured out
> > > > yet, Kern is God, and to question him, leaves you shunned, no matter
> > > > what your input was. Bacula is built on faith, not fact.
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > >---- ----- The Next 800 Companies to Lead America's Growth: New Video
> > > > Whitepaper David G. Thomson, author of the best-selling book
> > > > "Blueprint to a Billion" shares his insights and actions to help
> > > > propel your business during the next growth cycle. Listen Now!
> > > > http://p.sf.net/sfu/SAP-dev2dev
> > > > _______________________________________________
> > > > Bacula-devel mailing list
> > > > Bacula-devel@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/bacula-devel



------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to