[PATCH] resume-ndl_gsm.patch

Andy Green andy at openmoko.com
Fri Apr 4 18:26:14 CEST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| On Friday 04 April 2008 12:59:52 Andy Green wrote:
|> Somebody in the thread at some point said:
|
|> Maybe when you think a patch is complete, you can post it here, this
|> alerts everyone to what is being done and triggers it moving on.
|
| What is ready for your branch are the last three commits. But this is
where
| stuff is getting dirty. The first of the three is just applying one more
| patch (for the wolfson codec one to make alsactl happy), the other two
are
| diffs between the git version and my Linux tree as of the OpenEmbedded
build.

OK.

|> By all means post you recent patches that went into "andy" here too so
|> everyone can sync up on what goes on.
|
| I will do this, tonight or tomorrow night.

Great, thanks.

|> Also I just been tidying up metadata on mokopatches because we want to
|> make a stable history branch.  If you have any advice on git methodology
|> for that it's welcome.
|
| I will have to read up on what we want to do. I will give comments
once I know
| what we want.

Currently my branch and probably yours don't have real commit histories,
mine at least gets nuked around by stg according to what goes on and
then rewritten wholesale.  That's great for what we use them for.

But we can do with an new additional branch that isn't like that, it's
basically the openmoko equivalent of the kernel.org torvalds repo where
atomic patches get committed and the history is permanent and linear.
(If we didn't like a patch and need to throw it out, we have to make a
git revert "antipatch" and commit it -- hopefully this is uncommon).

But we have to take account of a living kernel.org then a frozen
mokopatch branch layer similar to how our branches work today.  It's
clear this is git's "bread and butter" but it's also clear there can be
many ways to get things done with git and some are better than others.
So any experience along these lines is gratefully received.

- -Andy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkf2VqYACgkQOjLpvpq7dMokYQCeJdRihhlTJM61TnCcuJMdG0mk
RugAnj6Q/E4BgIEEkG10oRPSV/nNDyI7
=fbSD
-----END PGP SIGNATURE-----




More information about the openmoko-kernel mailing list