[arch-dev-public] initscripts in testing

[Dan McGee]

On 10/19/07, Dan McGee <dpmcgee at gmail.com> wrote:
> On 10/19/07, Thomas Bächler <thomas at archlinux.org> wrote:
> > Aaron Griffin schrieb:
> > > Third thought. We should treat the initscripts as a real code project.
> > > That is, place them beside the rest of the code and create real
> > > tarballs.
> >
> > Agreed. Tell that to the guy who has permissions to create a new GIT
> > repository. I think his name was Aaron.
>
> I'll pull the CVS history sometime today so we can have some backlog
> in GIT. Post this release, we'll get it in a repository and do
> development from there, but I agree with tpowa that we should at least
> wait until this release is out to do shifting like that.

Hey Thomas- thanks for using the new GIT repo already, glad to see it
is being put to good use. Can you ensure that when you make a tarball
from it you tag the release? (git tag 2007.11 <sha1>) It would help in
the future when we want to look back at certain points in time, and I
tried as best I could to get all the old release points tagged as
well.

And I noticed your whitespace commit- if you enable the pre-commit
hook in your local repository, then you can prevent these things from
happening.

-Dan