Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] git feedback

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Jeremy Blosser <jblosser-smgl AT firinn.org>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] git feedback
  • Date: Fri, 28 Jul 2006 12:26:39 -0500

On Jul 28, Andra?? ruskie Levstik [ruskie AT mages.ath.cx] wrote:
> Jeremy Blosser wrote :
>
> > > ------- Additional Comment #6 From Seth Woolley 2006-07-27 16:32
> > > -------
> > >
> > > Yes, for changelogs, git's merges don't work. I'd almost prefer to have
> > > HISTORY be a git commit that took the commit info and auto-generated the
> > > HISTORY.
> >
> > It's been suggested before, and it's certainly doable, but the typical
> > response is that our HISTORY files are a different use case than the info
> > we want in the raw SCM changelog. That we keep history different places
> > in
> > different forms is intended as a feature. Arwed can speak to that more if
> > he wants...
> >
>
> What kind of info could there be autogenerated??? I mean will it read the
> devs mind on what he was fixing. I mean ok you can get what files were
> fixed and if maybe there was a version bump(just parse the VERSION in
> the diff) but the rest is kinda impossible.
> Like:
> * BUILD: completly overhauled it, made it use scons instead of make
> * DEPENDS: added FOO to be non-optional but this might change in the
> future so it shoud be checked on each update
>
> I just don't see having autogenerated HISTORY be so precise.

I would expect that the idea would be to have the commit message contain
the things that go into the HISTORY now along with the bug ids and such
that sometimes only get included in the commit message now.

Attachment: pgpLvnJbecbxD.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page