From: Jon Loeliger <jdl@freescale.com>
To: Git List <git@vger.kernel.org>
Subject: Checking git-cherry-pick Use Case
Date: Wed, 11 Jan 2006 10:46:07 -0600 [thread overview]
Message-ID: <1136997967.29751.198.camel@cashmere.sps.mot.com> (raw)
Guys,
Could you sanity check me on two issues with
my "work flow" here, please? Maybe I could do
something better/easier?
I have a repo with a bunch of commits coming from
several different places (me, co-worker, remote repo, etc).
I'm applying co-worker's patches into "cow" branch.
I'm applying my changes directly to "jdl" branch"
I'm pulling in "origin" crude.
Ultimately, I want to do development against the "sum total
set of all known patches supplied by anyone". Oh yeah.
So I make a "dev" branch that has "cow" + "jdl" + "origin".
However, at the end of the development day, I want to send
just _my_ patches upstream. Thus, I need to have my changes
sitting around neatly on the "jdl" branch.
I don't want to develop in the "jdl" branch, as it doesn't
have everything needed to test stuff properly (missing "cow"
code, eg.). So I actually edit and commit in the "dev"
branch where everything is unioned.
To isolate just my changes out of the "dev" branch into
the "jdl" branch, I cherry pick them like this:
$ git checkout dev
$ <do edit-compile-test cycle until all is well>
$ git commit -m "Stuff jdl made up and committed"
Now, things look, in part, like this:
! [dev] Stuff jdl made up and committed
* [jdl] Early stuff jdl made up
! [origin] Original stuff
---
+ [dev] Stuff jdl made up and committed
+ [dev^] Merge branch 'jdl'
++ [jdl] Early stuff jdl made up
+++ [origin] Original stuff
Then I pull that last "dev" commit over to "jdl":
$ git checkout jdl
$ git cherry-pick -r dev
Now it looks like this:
! [dev] Stuff jdl made up and committed
* [jdl] Early stuff jdl made up
! [origin] Original stuff
---
+ [jdl] Stuff jdl made up and committed
+ [dev] Stuff jdl made up and committed
+ [dev^] Merge branch 'jdl'
++ [jdl^] Early stuff jdl made up
+++ [origin] Original stuff
My first question is that I expected to see
something more like this (hand edited):
! [dev] Stuff jdl made up and committed
* [jdl] Early stuff jdl made up
! [origin] Original stuff
---
++ [dev] Stuff jdl made up and committed
+ [dev^] Merge branch 'jdl'
++ [jdl^] Early stuff jdl made up
+++ [origin] Original stuff
That is, the _same_ commit is now in both the "dev"
and "jdl" branches, so why does it have two lines here?
And finally, the "general" question: Is this a sane
work-flow used by anyone else? Or is there a different
perhaps even better way to do what I described above?
Thanks,
jdl
next reply other threads:[~2006-01-11 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 16:46 Jon Loeliger [this message]
2006-01-11 19:29 ` Checking git-cherry-pick Use Case Junio C Hamano
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=1136997967.29751.198.camel@cashmere.sps.mot.com \
--to=jdl@freescale.com \
--cc=git@vger.kernel.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