[Xorg] next steps with the xorg tree

[Kaleb S. KEITHLEY]

Kendall Bennett wrote:
> "Kaleb S. KEITHLEY" <kaleb at shiman.com> wrote:
> 
> 
>>Kendall Bennett noted that {RCS,CVS}ID strings in the sources make
>>it hard to import/merge changes into other people's trees. I
>>certainly agree -- after 10+ years working with X Consortium,
>>XFree86, and now Xorg trees doing imports and merges -- that it
>>does indeed make for more work. 
>>
>>So you have to tell me whether it's valuable or not to be able to
>>look at a file, possibly from somewhere else, and be able to tell
>>at a glance what its provenance is. 
> 
> 
> As I mentioned before, that is the realm of good source control systems. 
> I don't use CVS extensively so I don't know it works for CVS, but with 
> Perforce I can just do a 'p4 filelog' on any file and it will give me all 
> the history of that file, the change log comments and changelist numbers. 

It'll do this for any arbitrary file I happen to be looking at? Or just 
the files checked out in a P4 sandbox?

> With the changelist numbers I can find out what other files were checked 
> in at the same time for that change as well.

Now that's a nice feature.

> If CVS doesn't have these abilities, maybe we should consider using a 
> better tool for the job, like Perforce ;-)

Maybe the folks at perforce would like the good will and warm fuzzies 
they'd get from giving fd.o a license?

--

Kaleb