Thread (3 messages) 3 messages, 3 authors, 2006-01-09

RE: git pull on Linux/ACPI release tree

From: Brown, Len <hidden>
Date: 2006-01-09 05:53:56
Also in: linux-acpi, lkml

On 1/9/06, Brown, Len [off-list ref] wrote:
quoted
Perhaps the tools should try to support what "a lot of people"
expect, rather than making "a lot of people" do extra work
because of the tools?
I think it does. All the tricky stuff that David and Junio have been
discussing is actually done very transparently by

   git-rebase <upstream>

Now, git-rebase uses git-format-patch <options> | git-am <options> so
it sometimes has problems merging. In that case, you can choose to
either resolve the problem (see the doco for how to signal to git-am
that you've resolved a conflict) or to cancel the rebase. If you
choose to cancel the rebase, do

  cp .git/refs/heads/{<headname>,<headnamebadrebase>}
  cat .git/HEAD_ORIG > .git/refs/heads/<headname>
  git-reset --hard
  rm -fr .dotest

and you'll be back to where you started. Perhaps this could be rolled
into something like git-rebase --cancel to make it easier, but that's
about it. The toolchain definitely supports it.
This is completely insane.
Do you have any idea what "sometimes has problems merging" means
in practice?  It means the tools are really nifty in the trivial
case but worse than worthless when you need them the most.

-Len
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help