23 Aug
2008
23 Aug
'08
9:20 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
aymeric mansoux wrote:
Daniel James said :
I agree, let's start it slowly and see how it goes.
Concerning the directory structure, we use that for p:d:
http://code.goto10.org/projects/puredyne/browser/live/kernel
I like that trac ;)
Are there
intention for a [regular] /meeting/ (IRC)?
I don't think we need that yet,
unless a formal team is organised. I
could be wrong about that though ;-) a rather simple
kernel version
`- config
`- patches
maybe good enough for now?
yes, then this will become a /project/ by itself (not related to
kernel-git) and we may want add one folder depth:
VERSION -> MINORVERSION-<VENDOR> -> <files>
eg. 2.6.26 -> 2.6.26.2-dyne -> config & patches
in terms of who is pushing what to who, I would not
mind dropping the
kernel folder we have on our SVN and only work from one type of repos.
So, that means we would push stuff directly to the/a LAT git.
It doesn't make much sense to maintain 2 different type of repos for
that (SVN and git). What do you think Karsten? It's gonna be a pain to
move data from p:d SVN to a LAT git and back everytime we have a new
config commited I think.
git can import export from/to svn. It's actually very easy to use both
in parallel.
If you get the upstream kernel via git; you can get a /tagged vanilla/
and configure some /git-remotes/ to just pull in patches from
linuxaudio.org or wherever. - if
http://www.google.com/search?q=git+kernel+howto is not enough, we can
collect some /quick-start/ git command-lines on the wiki.
I'm running a trac with git backend elsewhere; and may just replicate
that on linuxaudio.org. We're not actively fixing bugs, but the
ticketing system may come in handy for quality control. - Well there's
also mantis, flyspray, etc. and *this* mailing list.. We'll also need
to think how to share content and accounts for these services.
(personally I'm pushing openID, oAuth, SSH-KEYs; and WikiRPCInterface2 )
If we need non LAT generic config, we can always have
distro
specific config files in another LAT git or in a subfolder, etc ...
We might have to experiment for a little while anyway, until we have
some workflow and structure that everyone is happy with :)
sure, learning by doing..
have a nice weekend,
robin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkiv8nkACgkQeVUk8U+VK0L5IACgutbhaerPnVaGeIlQip/JJoWm
8MMAn1QgMrrIxamLoeoQVWrSzU5sjFOi
=8Xla
-----END PGP SIGNATURE-----