RE: Amanda Sourceforge -> Amanda Github changeover

2019-04-05 Thread Chris Hassell
Git log is available all the time (and has been grandfathered accurately) and 
the sum total of changes can be read by

% git diff --stat tags/

... along with the log in the same way ...

% git log tags/

And those changes (from git log) should be helpfully summarized into the 
Changelog.

> -Original Message-
> [email protected]> On Behalf Of Gene Heskett
> Sent: Friday, April 5, 2019 11:04 AM

> > NOTE: The Changelog file(s) still need(s) to be maintained, but may be
> > more a running summary instead of a per-commit/rev match of the git
> > log.   Ideally each full revision/tag should get a complete and
> > accurate Changelog.

> That we haven't had in a while. It would be nice. We have a ChangeLog, but
> its hard to break it down to match it to the release, or is for me.




Re: Amanda Sourceforge -> Amanda Github changeover

2019-04-05 Thread Gene Heskett
On Monday 01 April 2019 12:28:41 Chris Hassell wrote:

> Greetings,
>
> I've gotten systems together to start moving Amanda development to be
> Github based alone.  This would allow us to start integrating pull
> requests more as normal and merging of changes from others who develop
> on our Github forks.
>
> Currently, every tag/branch that is present on Sourceforge/SVN is now
> a direct diff-match with the Github version.   If anyone out there has
> pulled the latest Github commits and sees any file differences on the
> shared branches/tags, please let me know.
>
> Older tags and branches should stay in sync now with changes added to
> Github, but new branches in Github will not be added to Sourceforge.
>
> NOTE: The Changelog file(s) still need(s) to be maintained, but may be
> more a running summary instead of a per-commit/rev match of the git
> log.   Ideally each full revision/tag should get a complete and
> accurate Changelog.
>
>
>   *   Christopher Hassell

That we haven't had in a while. It would be nice. We have a ChangeLog, 
but its hard to break it down to match it to the release, or is for me.



Copyright 2019 by Maurice E. Heskett
Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 



Re: Amanda Sourceforge -> Amanda Github changeover

2019-04-02 Thread Orion Poplawski
On 4/1/19 10:28 AM, Chris Hassell wrote:
> Greetings,
> 
> I’ve gotten systems together to start moving Amanda development to be Github
> based alone.  This would allow us to start integrating pull requests more as
> normal and merging of changes from others who develop on our Github forks.

That's welcome news.  I've updated my pull requests there.

-- 
Orion Poplawski
Manager of NWRA Technical Systems  720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   [email protected]
Boulder, CO 80301 https://www.nwra.com/



smime.p7s
Description: S/MIME Cryptographic Signature


Amanda Sourceforge -> Amanda Github changeover

2019-04-01 Thread Chris Hassell
Greetings,

I've gotten systems together to start moving Amanda development to be Github 
based alone.  This would allow us to start integrating pull requests more as 
normal and merging of changes from others who develop on our Github forks.

Currently, every tag/branch that is present on Sourceforge/SVN is now a direct 
diff-match with the Github version.   If anyone out there has pulled the latest 
Github commits and sees any file differences on the shared branches/tags, 
please let me know.

Older tags and branches should stay in sync now with changes added to Github, 
but new branches in Github will not be added to Sourceforge.

NOTE: The Changelog file(s) still need(s) to be maintained, but may be more a 
running summary instead of a per-commit/rev match of the git log.   Ideally 
each full revision/tag should get a complete and accurate Changelog.


  *   Christopher Hassell