From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Reconsidering the work flow and how the SCM system fits in
Date: Tue, 11 Mar 2008 11:38:07 +0100 [thread overview]
Message-ID: <fr5neg$l26$1@ger.gmane.org> (raw)
In-Reply-To: <20080311101433.77a09fd2@cimmeria>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Graeme Gregory schreef:
|> Nice, your argumentation is pretty convincing. I just guess that we're
|> going to have lots of "I'd love to see branches in OE" votes in this
|> thread, and I'd just love to see them treated separately from "I need
|> branches", "I'm ok with using branches for my changes", "Branches are
|> going to complicate my work, but I might try", and "I hate branches -
|> I already barely have time to do real work" votes.
|>
|
| I need branches.
Heh, I feel an "told you so" moment coming. The 'frozen revision'
approach could have more easily been a branch with no changes (except
for the branchpoint) that you or John only update (mtn propagate
org.openembedde.dev org.openmoko.lag) when you think .dev is buildable.
And it would also have been a natural place to stash things like your
qtopia stuff.
| I need to be able to have an openmoko branch which follows .dev closely
| but has some stuff that hasnt reached QA level required to allow in
| .dev yet.
|
| I probably need the openmoko branch to be only served by the openmoko
| servers.
|
| What I don't know is how this works with monotone, and I haven't had
| time to sit down with the manual and trial it.
The q&d way:
* create a local diff by editing or adding a file
* commit -b org.openmoko.needmorebru
* checkout the branch into a new dir: mtn co -b org.openmoko.needmorebru
* go wild in that branch
* track .dev: mtn propagate org.openembedded.dev org.openmoko.needmorebru
and once the stuff reached a good QA point:
mtn propagate org.openmoko.needmorebru org.openembedded.dev
That what stelios and I did with the avr32 branch and it works great.
The thing that stops the branch from being unmergable is the regular
propagate from .dev to org.openmoko.needmorebru.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH1mEPMkyGM64RGpERAkaDAJ0ZptVecmhKw+yLg3/j7I7I9YVo4ACfSpkB
aCJd/THz7BPIHwcH/5Ns2SI=
=m7A8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-11 10:40 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 7:07 Reconsidering the work flow and how the SCM system fits in Holger Freyther
2008-03-11 8:05 ` Koen Kooi
2008-03-11 9:42 ` Holger Freyther
2008-03-11 9:59 ` Koen Kooi
2008-03-11 10:24 ` Richard Purdie
2008-03-11 8:47 ` Esben Haabendal
2008-03-11 9:32 ` Paul Sokolovsky
2008-03-11 9:45 ` Holger Freyther
2008-03-11 10:00 ` Paul Sokolovsky
2008-03-11 10:14 ` Graeme Gregory
2008-03-11 10:38 ` Koen Kooi [this message]
2008-03-11 10:56 ` Holger Freyther
2008-03-11 11:21 ` Koen Kooi
2008-03-11 12:25 ` Holger Freyther
2008-03-11 12:38 ` Koen Kooi
2008-03-11 14:23 ` Florian Boor
2008-03-11 12:47 ` John Lee
2008-03-11 14:14 ` Holger Freyther
2008-03-11 16:11 ` Koen Kooi
2008-03-11 9:53 ` Koen Kooi
2008-03-11 13:43 ` Mike (mwester)
2008-03-11 9:41 ` Koen Kooi
2008-03-11 9:52 ` Paul Sokolovsky
2008-03-11 10:04 ` Holger Freyther
2008-03-11 10:25 ` Marcin Juszkiewicz
2008-03-11 10:46 ` Koen Kooi
2008-03-11 11:00 ` Richard Purdie
2008-03-11 12:30 ` Paul Sokolovsky
2008-03-11 12:39 ` Richard Purdie
2008-03-11 13:03 ` Paul Sokolovsky
2008-03-11 13:44 ` Richard Purdie
2008-03-11 14:01 ` Philip Balister
2008-03-11 15:39 ` Paul Sokolovsky
2008-03-11 16:15 ` Richard Purdie
2008-03-11 23:29 ` Paul Sokolovsky
2008-03-11 16:12 ` Tim Bird
2008-03-11 21:01 ` Rodrigo Vivi
2008-03-11 23:40 ` Paul Sokolovsky
2008-03-12 0:13 ` Richard Purdie
2008-03-11 14:13 ` Florian Boor
2008-03-11 11:49 ` Petr Stetiar
2008-03-11 12:23 ` Paul Sokolovsky
2008-03-11 13:24 ` Florian Boor
2008-03-11 13:39 ` Koen Kooi
2008-03-11 15:49 ` Paul Sokolovsky
2008-03-11 14:12 ` Cliff Brake
2008-03-11 14:57 ` Petr Stetiar
2008-03-11 15:49 ` Richard Purdie
2008-03-11 23:49 ` Paul Sokolovsky
2008-03-12 0:09 ` Richard Purdie
2008-03-12 0:44 ` Paul Sokolovsky
2008-03-12 18:38 ` Leon Woestenberg
2008-03-12 19:00 ` Koen Kooi
2008-03-12 19:09 ` Philip Balister
2008-03-12 20:10 ` Rodrigo Vivi
2008-03-12 20:26 ` Leon Woestenberg
2008-03-12 20:45 ` Koen Kooi
2008-03-12 20:50 ` Stelios Koroneos
2008-03-12 21:34 ` Paul Sokolovsky
2008-03-12 21:54 ` Richard Purdie
2008-03-12 22:54 ` Koen Kooi
2008-03-12 23:24 ` Leon Woestenberg
2008-03-13 0:44 ` Richard Purdie
2008-03-13 8:53 ` Koen Kooi
2008-03-13 11:52 ` Florian Boor
2008-03-13 8:48 ` Marcin Juszkiewicz
2008-03-13 0:18 ` Rod Whitby
2008-03-13 0:59 ` Richard Purdie
2008-03-13 1:22 ` Rod Whitby
2008-03-13 6:33 ` Hans Henry von Tresckow
2008-03-12 21:11 ` Richard Purdie
2008-03-12 21:21 ` Koen Kooi
2008-03-12 21:40 ` Paul Sokolovsky
2008-03-12 22:07 ` Leon Woestenberg
2008-03-12 22:32 ` Paul Sokolovsky
2008-03-13 11:29 ` Marcin Juszkiewicz
2008-05-02 5:30 ` Justin Patrin
2008-03-12 21:49 ` Richard Purdie
2008-03-12 21:37 ` Mikhail Gusarov
2008-03-13 22:29 ` Dmitry Nezhevenko
2008-03-11 13:55 ` Mikhail Gusarov
2008-03-11 10:53 ` Richard Purdie
2008-03-11 11:19 ` Graeme Gregory
2008-03-11 13:17 ` Florian Boor
2008-03-11 12:04 ` Florian Boor
2008-03-11 13:09 ` Mike (mwester)
-- strict thread matches above, loose matches on Subject: below --
2008-03-12 20:34 Mike Westerhof
2008-03-12 20:47 ` Mikhail Gusarov
2008-03-12 20:59 ` Rodrigo Vivi
2008-03-12 21:20 ` Koen Kooi
2008-03-12 21:52 ` Mark Brown
2008-03-12 22:03 Mike Westerhof
2008-03-12 22:21 ` Paul Sokolovsky
2008-05-02 5:46 ` Justin Patrin
2008-03-12 22:48 Mike Westerhof
2008-03-12 23:10 ` Paul Sokolovsky
2008-03-12 23:18 ` Richard Purdie
2008-03-13 0:45 ` Rod Whitby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fr5neg$l26$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox