[SCM TRANSITION] Re: Proposal: move Randr protocol and library to git
eich at suse.de
Wed Apr 19 01:12:14 PDT 2006
Daniel Stone writes:
> > At least with CVS as currently set up you can do this all with one commit.
> > This is because drivers/ is the super module of all individual drivers.
> > If the changes are related - as in your case - this should not be considered
> > a policy violation.
> I, for one, would very much like it if it were.
Is there a point in that if you make the same change to every driver
you do this in a separate commit?
How about the bugzilla triage? If you extend the driver API and make
every driver in our code base take advantage of this would you go as
far as making it a requirement to file every (contextually identical)
change as a separate ticket?
Can the bugzilla be made scriptable?
> > The only additional work required is to modify the ChangeLogs of each driver.
> > This can be automated by hacking the prepate-Changelog.pl script.
> > Apart from this there is no more work than in a situation where we kept a
> > number of drivers in a single module.
> If you're scripting the changelog anyway, why not just script the
> commits? It's a trivial leap.
I have always refrained from this. For some reason commits in CVS
were a scary process (sometimes we used development snapshots of
CVS which would stumble and fall on the floor leaving all sorts of
garbage behind). Thus I wanted to retain as much control as possible.
But this is no argument against the possiblitiy of scripting this
- and maybe things become less scary with a new SCM.
More information about the xorg