git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: keeping track of where a patch begins

From
Nicolas Pitre <nico@fluxnic.net>
Date
Oct 21, 2009, 18:14 UTC
Message-ID
<alpine.LFD.2.00.0910211402490.21460@xanadu.home>
In-Reply-To
<3a69fa7c0910210745r311cf18xf966f5c63650cde6@mail.gmail.com>
On Wed, 21 Oct 2009, E R wrote:
> What solutions have you come up with to either to catch or prevent
> this from happening? It is possible to determine what node a branch
> started from?
This can be determined by looking at the gitk output.

Also 'git merge-base' can give you that node, given the main branch and the topic branch. See documentation about git-merge-base.

Then if you need to move a branch to another starting node, then 'git rebase' is what you need (again the git-rebase documentation is pretty detailed).

Nicolas
Previous: E RNext: Junio C Hamano
Message 2 of 8 in “keeping track of where a patch begins”
  1. E ROct 21, 2009
  2. Nicolas PitreOct 21, 2009
  3. Junio C HamanoOct 21, 2009
  4. Nicolas PitreOct 21, 2009
  5. Thomas RastOct 22, 2009
  6. Pascal ObryOct 30, 2009
  7. Thomas RastOct 30, 2009
  8. Jeff KingOct 26, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.