linux-fbdev-devel

[Linux-fbdev-devel] cvs checkins

[Geert U. <ge...@li...>]

I think it's worthwhile to feed CVS checkin logs to a mailing list.
Should I feed them to linux-fbdev-devel, or create a new list for them?

Contrary to the docs on SourceForge, it doesn't seem to be possible to create a
list with name *-cvs. The mailing list manager complains about a too short list
name.

BTW, I'd like to see more drivers in CVS :-) I plan to check in the new atyfb
(the one in Alan's tree) soon.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: [Linux-fbdev-devel] cvs checkins

[Romain D. <do...@ir...>]

Geert Uytterhoeven wrote:

> BTW, I'd like to see more drivers in CVS :-) I plan to check in the new atyfb
> (the one in Alan's tree) soon.

Mmmm, is there a way in CVS to give per-module write access ? If not,
that means you have to trust everyone for everything, or to have
every patch goes through a few people...

Also, can an import preserve existing CVS info like branch, revision
number and the like ? (pm3fb is ATM on a private CVS, I'd like to be
able to keep the history if it moves to linux-fbdev on SourceForge)

-- 
DOLBEAU Romain               | l'histoire est entierement vraie, puisque
ENS Cachan / Ker Lann        |     je l'ai imaginee d'un bout a l'autre
do...@ir...             |           -- Boris Vian

Re: [Linux-fbdev-devel] cvs checkins

[Geert U. <ge...@li...>]

On Wed, 25 Apr 2001, Romain Dolbeau wrote:
> Geert Uytterhoeven wrote:
> > BTW, I'd like to see more drivers in CVS :-) I plan to check in the new atyfb
> > (the one in Alan's tree) soon.
> 
> Mmmm, is there a way in CVS to give per-module write access ? If not,
> that means you have to trust everyone for everything, or to have
> every patch goes through a few people...

Yep, we have to trust whoever has checkin rights. I don't think that will be a
big problem, though.

> Also, can an import preserve existing CVS info like branch, revision
> number and the like ? (pm3fb is ATM on a private CVS, I'd like to be
> able to keep the history if it moves to linux-fbdev on SourceForge)

According to the SourceForge docs, you have to ask a human at SourceForge to
import your existing repository.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: [Linux-fbdev-devel] cvs checkins

[Romain D. <do...@ir...>]

Geert Uytterhoeven wrote:

> Yep, we have to trust whoever has checkin rights. I don't think that will be a
> big problem, though.

If all driver devellopers have write access, it might cause trouble,
simply because CVS is not foolproof. I know I almost blowed up
my CVS tree once because of a typing mistake... those can happen to
everyone, in particular when you finally sort out a bug at 3 AM :-)

> According to the SourceForge docs, you have to ask a human at SourceForge to
> import your existing repository.

Yuck...

Any point in trying to import pm3fb in SourceForge ? There isn't much
interest in using it, it seems ; not a single report in two months of
puclic availability, out of close to a hundred uniques domains accessing
the web page :-(

-- 
DOLBEAU Romain               | l'histoire est entierement vraie, puisque
ENS Cachan / Ker Lann        |     je l'ai imaginee d'un bout a l'autre
do...@ir...             |           -- Boris Vian