On Wed, 30 Apr 2008 12:27:25 -0700, Russ Allbery <[EMAIL PROTECTED]> said:
> While preparing the next release, should I delete ChangeLog and
> debian/ChangeLog? It doesn't look like either have been used in a
> while, and since we're using a VCS that records all that information
> with more detail, I wouldn't think we'd want to use it in the future.
I'd be fine with that. git log <filename> is probably better --
as long as out commit messages are descriptive, which they should be,
really.
> Also, debian/postinst.in, debian/prerm.in, and debian/rules have
> headers that look like they're normally managed with Emacs modes or
> something similar, but which haven't been updated in some time and are
> probably redundant with a VCS at this point. Should I remove those as
> well to avoid any possible confusion?
I would like that. They are my emacs macros, and the thing is,
when I commit to a file, the headers change -- so when there are
commits that I make to the same file in more than one branch, there is
an instant conflict -- since the headers are changed on both branches,
and the lines overlap.
I really should get rid of the macros, but nostalgia keeps me
from doing so. I mean, how else could I tell that my .login was created
on an ULTRIX box in July '88?
manoj
this means that ~/.login is older than some people on this mailing list
--
"One day I woke up and discovered that I was in love with tripe." Tom
Anderson
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
