Petr Rockai <[EMAIL PROTECTED]> writes: > But, as an alternative, I propose that if someone picks up the weekly > news, they, with every issue, tag the darcs repository with > news-YYYY-MM-DD, whoever ends up writing the final changelog can: > > $ darcs changes --from-tag=<prev-release> --tag news > <rip out the interesting bits from those news entries> > > $ darcs changes --from-tag=news > which ideally would contain very few changes > > Ideally, news-n would ideally cover everything since news-(n-1) for > this to work usefully.
While the approach sounds useful, I'm not sure I'd be happy about a whole bunch of news-X tags showing up in the main repository. Could you (Petr) keep the news-X tags in a local branch, as a "here's where I'm up to" note? You'd start with by recording a change to NEWS with -m "News as at 2008-12-04" and then amend it to "News as at 2008-12-11" and eventually "News as at 2.1.1", or whatever the next tagged release/pre-release/release-candidate is. Only this final patch would enter the http://darcs.net/ repository, i.e. one NEWS patch per release, entering just before the release is tagged. I'm assuming that the NEWS is mainly useful for releases, and there is no need to keep the NEWS file "up to date" for people who are tracking the unreleased repo. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
