Menu
▾
▴
linux-apus-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(210) |
Jun
(169) |
Jul
(167) |
Aug
(128) |
Sep
(218) |
Oct
(120) |
Nov
(86) |
Dec
(71) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(91) |
Feb
(179) |
Mar
(52) |
Apr
(56) |
May
(183) |
Jun
(62) |
Jul
(63) |
Aug
(49) |
Sep
(36) |
Oct
(35) |
Nov
(72) |
Dec
(30) |
| 2002 |
Jan
(53) |
Feb
(61) |
Mar
(56) |
Apr
(13) |
May
(1) |
Jun
(7) |
Jul
(80) |
Aug
(73) |
Sep
(30) |
Oct
(29) |
Nov
(8) |
Dec
(40) |
| 2003 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(19) |
Jul
(64) |
Aug
(53) |
Sep
(28) |
Oct
(7) |
Nov
(3) |
Dec
(21) |
| 2004 |
Jan
(11) |
Feb
(30) |
Mar
(18) |
Apr
(1) |
May
(13) |
Jun
(18) |
Jul
(13) |
Aug
|
Sep
(9) |
Oct
(5) |
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(21) |
Sep
(7) |
Oct
(10) |
Nov
(6) |
Dec
|
| 2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(6) |
Oct
(10) |
Nov
(8) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(6) |
Mar
(1) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(13) |
Aug
(8) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Michel <dae...@st...> - 2000-05-29 08:48:26
|
Frank Petzold wrote: > > On Mon, May 29, 2000 at 10:34:39AM +0200, Michel Dänzer wrote: > > Do changes to the trunk get applied to the branch? > > You can merge them. But unless one merges them, the branch 'stands still' except for the files one works on? > > Should we announce when we start a branch? > > No, we need to announce before merging. Alright. Michel -- Pauli's exclusive, Heisenberg's uncertain, and Schroedinger just waves. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Michel <dae...@st...> - 2000-05-29 08:46:33
|
Another thing that might be handy in CVS is the web site. I'm planning to change things to use a template (probably using PHP) so that the pages are easy to set up and everything stays consistent. Michel -- Man invented language to satisfy his deep need to complain. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Frank P. <fp...@zu...> - 2000-05-29 08:42:35
|
On Mon, May 29, 2000 at 10:34:39AM +0200, Michel Dänzer wrote: > Do changes to the trunk get applied to the branch? You can merge them. > Should we announce when we start a branch? No, we need to announce before merging. -- Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4, CH-8803 Rüschlikon/Switzerland, Tel. +41-1-724-84-42 Fax. +41-1-724-89-56 Business email: fp...@zu... Private email: pe...@he... The opinions expressed here are mine and not necessarily those of IBM. |
|
From: Michel <dae...@st...> - 2000-05-29 08:36:45
|
Frank Petzold wrote: > You can split off a branch (cvs tag -b ken_tylers_53c7xx_changes) and > cvs upd -r ken_tylers_53c7xx_changes > > And then work with the repository as normal. Your commits will not disturb > anybody else that checks out the trunk. If the changes are stable enough to > go into "public" you can merge them into the trunk. Do changes to the trunk get applied to the branch? > I propose a branch for every "project" e.g. CV64/3D driver, 53c7xx.c, ect. Should we announce when we start a branch? Another thing I wonder about: Would it be reasonable to let CVS post to this list automatically upon each commit? Michel, who wishes his posts wouldn't only contain questions :) -- The computer revolution is over. The computers won. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Jesper S. <js...@re...> - 2000-05-29 08:28:10
|
>>>>> "Frank" == Frank Petzold <fp...@zu...> writes: Frank> On Mon, May 29, 2000 at 06:59:55AM +1000, Ken Tyler wrote: >> I'd like to ask how other people manage their own tree, how do you >> stay in sync with the repositry *AND* still keep local work from >> being lost - like my life time job on 53c7xx.c and related files ? Frank> You can split off a branch (cvs tag -b Frank> ken_tylers_53c7xx_changes) and cvs upd -r Frank> ken_tylers_53c7xx_changes Everybody having write access to the CVS tree should start by reading some CVS manuals. It's a reasonable requirement! Second, at Cygnu^H^H^H^H^HRed Hat we tag the tree before making a branch. I suspect because it makes it easier to pinpoint what went into a branch (the kind of information you'll only ever need if you didn't tag the tree). This is how we do it: cvs tag ken_tylers_53c7xx_changes-branchpoint cvs tag -b ken_tylers_53c7xx_changes-branch Remember to be at the top of the tree when doing this. Jesper |
|
From: <fp...@zu...> - 2000-05-29 07:02:42
|
On Mon, May 29, 2000 at 06:59:55AM +1000, Ken Tyler wrote: > I'd like to ask how other people manage their own tree, how do you stay in > sync with the repositry *AND* still keep local work from being lost - like > my life time job on 53c7xx.c and related files ? You can split off a branch (cvs tag -b ken_tylers_53c7xx_changes) and cvs upd -r ken_tylers_53c7xx_changes And then work with the repository as normal. Your commits will not disturb anybody else that checks out the trunk. If the changes are stable enough to go into "public" you can merge them into the trunk. Of course, if somebody wants to work with your changes, he can checkout your branch, too. I propose a branch for every "project" e.g. CV64/3D driver, 53c7xx.c, ect. -- Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4, CH-8803 Rüschlikon/Switzerland, Tel. +41-1-724-84-42 Fax. +41-1-724-89-56 Business email: fp...@zu... Private email: pe...@he... The opinions expressed here are mine and not necessarily those of IBM. |
|
From: Ken T. <ke...@we...> - 2000-05-29 06:57:21
|
On Mon, 29 May 2000, Geert Uytterhoeven wrote: > `cvs -z3 update -d', to enable compression and create new directories. Worked out the -d was required to create new/missing directories after a few tries. Was more concerned about losing my local changes. Ken. |
|
From: Geert U. <ge...@li...> - 2000-05-29 06:56:39
|
On Mon, 29 May 2000, Ken Tyler wrote: > On 28 May 2000, Jesper Skov wrote: > > lost. Worst case it will try to merge your work with stuff from the > > repository if the work affect the same lines of a file - but then it > > will notify you of a conflict (C) and leave both versions in the file > > marked by <<<<<<<<<<<< and >>>>>>>>>>>>>. > > Hello, > > 'C' ? > > Is this is one of the characters on the start of each line ? Yes, `C' means conflict. IIRC, there's a good tutorial on CVS at http://www.cyclic.com/. 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 |
|
From: Ken T. <ke...@we...> - 2000-05-29 06:50:28
|
On 28 May 2000, Jesper Skov wrote: > Just regular cvs update. It will not cause local work to be > lost. Worst case it will try to merge your work with stuff from the > repository if the work affect the same lines of a file - but then it > will notify you of a conflict (C) and leave both versions in the file > marked by <<<<<<<<<<<< and >>>>>>>>>>>>>. Hello, 'C' ? Is this is one of the characters on the start of each line ? > Still, it's a good idea to do occasional diffs (cvs diff -u) and keep > them around (backups). OK ken. |
|
From: Geert U. <ge...@li...> - 2000-05-29 06:46:48
|
On Sun, 28 May 2000, Nicholai Benalal wrote:
> Yes, I'm planning to do that once I've installed ssh under amigaos. (I've
> already thought about crosscompilation but it's too much of a mess trying to
> install crosscompilers for amigaos-m68k, amigaos-ppc-pup and
> amigaos-ppc-wup). The geekgadgets environment works just fine for me.
But once you have the crosscompiler, life becomes much simpler.
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
|
|
From: Geert U. <ge...@li...> - 2000-05-29 06:26:06
|
On 28 May 2000, Jesper Skov wrote:
> Ken> I'd like to ask how other people manage their own tree, how do
> Ken> you stay in sync with the repositry *AND* still keep local work
> Ken> from being lost - like my life time job on 53c7xx.c and related
> Ken> files ?
>
> cvs update
`cvs -z3 update -d', to enable compression and create new directories.
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
|
|
From: Jesper S. <js...@re...> - 2000-05-28 21:20:25
|
>>>>> "Ken" == Ken Tyler <ke...@we...> writes: Ken> Hi, Ken> I'm still on the bottom of the learning curve regarding all the Ken> CVS magic. Ken> I'd like to ask how other people manage their own tree, how do Ken> you stay in sync with the repositry *AND* still keep local work Ken> from being lost - like my life time job on 53c7xx.c and related Ken> files ? cvs update Just regular cvs update. It will not cause local work to be lost. Worst case it will try to merge your work with stuff from the repository if the work affect the same lines of a file - but then it will notify you of a conflict (C) and leave both versions in the file marked by <<<<<<<<<<<< and >>>>>>>>>>>>>. Still, it's a good idea to do occasional diffs (cvs diff -u) and keep them around (backups). Jesper |
|
From: Nicholai B. <nic...@ch...> - 2000-05-28 21:15:16
|
Hello Ken Den 28-Maj-00, skrev Ken Tyler: KT> Shouldn't we try to follow this new approach ? KT> KT> That was my intention. KT> Yes :-)). I just thought that the gfx based installer was a completely different source tree. That's why I questioned the need to u/l the old installer to the CVS (but I trust you to know a lot more than me when it comes to the installer so maybe I should just keep quiet ;-). Friendly, Nicholai |
|
From: Ken T. <ke...@we...> - 2000-05-28 21:11:33
|
On Sun, 28 May 2000, Nicholai Benalal wrote: > The problem is that linuxppc seems to move away from the text based > installer (that's at least what I heard). Nothing prevents you from > continuing to improve that installer but it will be harder and harder > with every new release. Shouldn't we try to follow this new approach ? That was my intention. Ken. |
|
From: Ken T. <ke...@we...> - 2000-05-28 21:02:31
|
Hi, I'm still on the bottom of the learning curve regarding all the CVS magic. I'd like to ask how other people manage their own tree, how do you stay in sync with the repositry *AND* still keep local work from being lost - like my life time job on 53c7xx.c and related files ? ken |
|
From: Nicholai B. <nic...@ch...> - 2000-05-28 21:01:45
|
Hello Ken Den 28-Maj-00, skrev Ken Tyler: KT> KT> KT> On Sun, 28 May 2000, Nicholai Benalal wrote: KT> KT>> That's up to Ken to decide but it would be nice. I remember all the KT>> trouble I had when trying to help Ken. Having said that, I don't know KT>> if the installer will change much in the future. KT> KT> Can't work out what you mean here, the installer is never finished KT> because every new CD does something different. Would be nice to get a KT> few Megs of space on the CD and have my changes integrated in the the KT> 'real' installer. KT> The problem is that linuxppc seems to move away from the text based installer (that's at least what I heard). Nothing prevents you from continuing to improve that installer but it will be harder and harder with every new release. /Nicholai |
|
From: Ken T. <ke...@we...> - 2000-05-28 20:56:54
|
On Sun, 28 May 2000, Nicholai Benalal wrote: > That's up to Ken to decide but it would be nice. I remember all the > trouble I had when trying to help Ken. Having said that, I don't know > if the installer will change much in the future. Can't work out what you mean here, the installer is never finished because every new CD does something different. Would be nice to get a few Megs of space on the CD and have my changes integrated in the the 'real' installer. Ken. |
|
From: Ken T. <ke...@we...> - 2000-05-28 20:51:21
|
On Sun, 28 May 2000, Michel [iso-8859-1] Dänzer wrote: > Nicholai, are you going to import boothack into the repository as well? > > And what about other stuff (LinuxPPC installer, ...) ? I'll put up the current 1999 installer, - I ordered the 2000 CD a couple of days ago so I'll have another one soon/eventually depending on whats needed. Do you want two installers on sourceforge ? (Not breaking any copyright are we ?) Ken. |
|
From: Nicholai B. <nic...@ch...> - 2000-05-28 15:28:37
|
Hello Michel Den 28-Maj-00, skrev Michel Dänzer: MD> MD> MD> Nicholai, are you going to import boothack into the repository as well? MD> Yes, I'm planning to do that once I've installed ssh under amigaos. (I've already thought about crosscompilation but it's too much of a mess trying to install crosscompilers for amigaos-m68k, amigaos-ppc-pup and amigaos-ppc-wup). The geekgadgets environment works just fine for me. MD> And what about other stuff (LinuxPPC installer, ...) ? MD> That's up to Ken to decide but it would be nice. I remember all the trouble I had when trying to help Ken. Having said that, I don't know if the installer will change much in the future. /Nicholai |
|
From: Michel <dae...@st...> - 2000-05-28 15:12:34
|
Nicholai, are you going to import boothack into the repository as well?
And what about other stuff (LinuxPPC installer, ...) ?
Michel
--
Software is like sex; it's better when it's free
-- Linus Torvalds
______________________________________________________________________________
Michel Dänzer /// mda...@ea...
__ /// AmigaOS/Linux(Debian/PPC)
Student of computer science at the \\\/// Team *AMIGA* ICQ #: 5675698
Swiss Federal Institute of Technology \\\/ AUGS member #163 IRC: CoOpER
|
|
From: Michel <dae...@st...> - 2000-05-28 15:09:18
|
Michel Dänzer wrote:
> > MD> - add PCI support for Permedia2 graphics boards
> > MD> - unify pm2fb
> >
> > Good!
>
> I must confess though that I haven't been able to test it in its final form.
> Can anybody confirm that it works?
I've just realized I forgot to commit arch/ppc/kernel/Makefile ... If anyone
wants to test it before I can fix that, please add apus_pci.o in the
appropriate place.
However, I'm very impressed by CVS. It merged Nicholai's and my changes in
apus_setup.c without me even noticing it.
Michel
--
Software is like sex; it's better when it's free
-- Linus Torvalds
______________________________________________________________________________
Michel Dänzer /// mda...@ea...
__ /// AmigaOS/Linux(Debian/PPC)
Student of computer science at the \\\/// Team *AMIGA* ICQ #: 5675698
Swiss Federal Institute of Technology \\\/ AUGS member #163 IRC: CoOpER
|
|
From: Michel <dae...@st...> - 2000-05-28 14:44:08
|
Nicholai Benalal wrote:
> MD> - add PCI support for Permedia2 graphics boards
> MD> - unify pm2fb
>
> Good!
I must confess though that I haven't been able to test it in its final form.
Can anybody confirm that it works?
> We are a bit different than the rest of the world. All development takes
> place in the stable tree.
:)
I'll (try to) do the same in 2.3 soon.
Michel
--
Software is like sex; it's better when it's free
-- Linus Torvalds
______________________________________________________________________________
Michel Dänzer /// mda...@ea...
__ /// AmigaOS/Linux(Debian/PPC)
Student of computer science at the \\\/// Team *AMIGA* ICQ #: 5675698
Swiss Federal Institute of Technology \\\/ AUGS member #163 IRC: CoOpER
|
|
From: Nicholai B. <nic...@ch...> - 2000-05-28 07:02:54
|
Hello Michel Den 28-Maj-00, skrev Michel Dänzer: MD>> I've now commited the patch to the CVS. MD> MD> Didn't last long, Took me little time to do it for 2.2 since I already had a diff but I'll wait with 2.3. Tried to compile 2.3 and it resulted in some error about a missing rule for autoconfig.h. No time to look into it. Does anyone know what should be done? 've committed some new stuff: MD> MD> - add PCI support for Permedia2 graphics boards MD> - unify pm2fb MD> Good! We are a bit different than the rest of the world. All development takes place in the stable tree. /Nicholai |
|
From: Michel <dae...@st...> - 2000-05-28 01:19:28
|
Nicholai Benalal wrote: > KT> Might be getting ahead of myself here but the patch to > KT> /arch/ppc/kernel/apus_setup.c posted recently by Nicholai is missing > KT> from the 2.2 tree on sourceforge. > > I've now commited the patch to the CVS. Didn't last long, I've committed some new stuff: - add PCI support for Permedia2 graphics boards - unify pm2fb CVS: Modified Files: CVS: drivers/video/pm2fb.c drivers/video/Config.in CVS: arch/ppc/config.in arch/ppc/kernel/apus_setup.c CVS: Added Files: CVS: arch/ppc/kernel/apus_pci.c arch/ppc/kernel/apus_pci.h Michel -- To boldly go where I surely don't belong. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
|
From: Nicholai B. <nic...@ch...> - 2000-05-27 23:19:52
|
*** Vidaresänt brev, ursprungligen skrivet av Nicholai Benalal den 28-Maj-00 *** Hello Ken Den 27-Maj-00, skrev Ken Tyler: KT> KT> KT> Hello, KT> KT> Might be getting ahead of myself here but the patch to KT> /arch/ppc/kernel/apus_setup.c posted recently by Nicholai is missing KT> from the 2.2 tree on sourceforge. KT> I've now commited the patch to the CVS. /Nicholai *** End of forwarded message *** |
107 messages has been excluded from this view by a project administrator.
