Skip to Content.
Sympa Menu

sm-commit - Re: [SM-Commit] GIT changes to master quill by Jaka Kranjc (912afa0ed45211b1208f279739239822676e1778)

sm-commit AT lists.ibiblio.org

Subject: Source Mage code commit list

List archive

Chronological Thread  
  • From: seth AT swoolley.homeip.net
  • To: Andra AT swoolley.homeip.net
  • Cc: sm-commit AT lists.ibiblio.org
  • Subject: Re: [SM-Commit] GIT changes to master quill by Jaka Kranjc (912afa0ed45211b1208f279739239822676e1778)
  • Date: Sun, 6 Aug 2006 18:25:40 -0700

On Mon, Aug 07, 2006 at 12:35:13AM +0200, Andra?? ruskie Levstik wrote:
> seth AT swoolley.homeip.net wrote :
>
> > instead of doing:
> > * FILE: entry
> > entry2
> > entry3 ...........................
> > continuation of entry3
> >
> > my historyfix script doesn't understand the continuation indent, so would
> > be better:
> >
> > * FILE: entry; entry2; entry3 .....................
> > continuation of entry3
> >
> > unless we want my script to ignore those. An alternative is:
> > * FILE:
> > * entry
> > * entry2
> > * entry3 ..................................
> > continuation of entry3
> >
> > but that doesn't work since it pulls them back assuming they are
> > misindented
> > first-level asterisks.
> >
> > I can change its behavior, but I just need a consistent plan for how to
> > attack it.
> >
> > Seth
> >
> I find it easier to check the logs if they have extra indentation like
> that but I'd like to know what the proper official ChangeLog layout is
> like. If that says space_space then I see no prob in reformating it to
> such.
>
> One could use "-" as a second level marker instead of the "*".
>
> But if the official ChangeLog format states the use of double spaces
> then as said it'll be fixed to comply.

That works well, - as second-level indent should work fine:

* FILE: overall decription
- entry1
- entry2




Archive powered by MHonArc 2.6.24.

Top of Page