Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] HISTORY file updates

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Eric Sandall <eric AT sandall.us>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] HISTORY file updates
  • Date: Tue, 13 Apr 2004 08:47:55 -0700

Quoting Seth Alan Woolley <seth AT positivism.org>:
> I just stepped on everybody's toes and committed two huge fixes to devel
> and test for HISTORY files.

Thanks for the cleanup Seth. ;)

> I also updated the wiki to clarify the HISTORY file format:
>
> --begin--
>
> 2003-10-13[ONE-SPACE]Name[ONE-SPACE]<your e-mail>
>
> [ONE-TAB]*[ONE-SPACE]<comma-space-delimited-file(s)>:[ONE-SPACE]Description
> of similar changes.
> [BLANK LINE HERE]
> 2003-10-08[ONE-SPACE]Name[ONE-SPACE]<your e-mail>
>
> [ONE-TAB]*[ONE-SPACE]<comma+space-delimited-file(s)>:[ONE-SPACE]Description
> of similar changes.
>
> [ONE-TAB]*[ONE-SPACE]<comma+space-delimited-file(s)>:[ONE-SPACE]Description
> of similar changes
> [ONE-TAB][TWO-SPACES]continuing on another line.
> [BLANK LINE HERE]
>
> --end--

That looks like a more refined definition of what we wanted. Any comments?

> You'll note the changes that I mention that files are delimited with
> comma and space and that line continuations take tab-space-space in
> front of the continuation lines, and that I have a period put at the end
> of the descriptions.
>
> I made a script to convert the old format to the new format and I
> happened to enforce the tab-space-space continuation rule by sheer
> reason that I had to pick one for my script to make things look neat.
>
> I only enforced the spacing between and among entries and the order of
> information in the date/name/email line in my script. Inserting files
> modified and putting periods at the ends of sentences was ignored. I
> also didn't enforce any specified maximum length of description strings,
> although we might consider that. A while ago I fixed the sorcery
> ChangeLog for long lines by hand.
>
> To make future mass updates go a bit smoother for people, I'll suggest
> running a p4 edit on any file you're even considering editing. That's a
> reservation that people doing mass edits should be especially careful
> to heed, and toes will be safer.

That should be SOP (unless the file's been open for a while (say two weeks,
but
then you should contact them and find out why).

> I hope that since I didn't touch anybody's sacred interpreted "code"
> that I haven't intruded too much and people will enjoy the cleaner
> history entries.

We've been doing the cleansing slowly, but now it's all nice and neat. :)

> Wow, I think my wife's rubbing off on me. If you had known me ten years
> ago, you'd never figure me for somebody so anal about things being neat.

Sounds like she's having a good effect on you. ;)

> Seth

-sandalle

--
PGP Key Fingerprint: FCFF 26A1 BE21 08F4 BB91 FAED 1D7B 7D74 A8EF DD61
http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA8EFDD61

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS/E/IT$ d-- s++:+>: a-- C++(+++) BL++++VIS>$ P+(++) L+++ E-(---) W++ N+@ o?
K? w++++>-- O M-@ V-- PS+(+++) PE(-) Y++(+) PGP++(+) t+() 5++ X(+) R+(++)
tv(--)b++(+++) DI+@ D++(+++) G>+++ e>+++ h---(++) r++ y+
------END GEEK CODE BLOCK------

Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




Archive powered by MHonArc 2.6.24.

Top of Page