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

Re: Questions about branches in git

From
Nicolas Pitre <nico@fluxnic.net>
Date
Jan 28, 2010, 22:04 UTC
Message-ID
<alpine.LFD.2.00.1001281656440.1681@xanadu.home>
In-Reply-To
<69b754db1001281317o69f8c3f9y412a8524407bacbf@mail.gmail.com>
On Thu, 28 Jan 2010, Mike Linck wrote:
Show 6 quoted lines
> Well, even gitk can't show me the information I'm looking for if the
> parent branch ended up fast-forwarding to include the changes made in
> the topic branch.  As far as I can tell there is *no way* to tell what
> changes were made in a particular branch after a fast-forward has
> taken place, which seems to make it hard to organize fixes for
> specific topics/bugs/tickets.

You should consider using tags in conjunction with your bugs/tickets system. The fork point for a bug fix may be tagged, as well as the last commit representing the bugfix completion (not the merge point though). This way you can always retrieve the exact set of commits forming up that bugfix, regardless if it was merged back into the main branch with a fast forward or not.

Nicolas
Previous: Junio C HamanoNext: Eugene Sajine
Message 11 of 21 in “Questions about branches in git”
  1. Mike LinckJan 28, 2010
  2. Michael WittenJan 28, 2010
  3. Michael WittenJan 28, 2010
  4. Michael WittenJan 28, 2010
  5. Mike LinckJan 28, 2010
  6. Jens LehmannJan 28, 2010
  7. Mike LinckJan 28, 2010
  8. Heiko VoigtJan 28, 2010
  9. Nanako ShiraishiJan 29, 2010
  10. Junio C HamanoJan 29, 2010
  11. Nicolas PitreJan 28, 2010
  12. Eugene SajineJan 28, 2010
  13. David AguilarJan 28, 2010
  14. Michael WittenJan 28, 2010
  15. Mike LinckJan 28, 2010
  16. Michael WittenJan 28, 2010
  17. Peter KreftingJan 29, 2010
  18. Martin LanghoffJan 28, 2010
  19. Junio C HamanoJan 28, 2010
  20. Mike LinckJan 29, 2010
  21. Peter KreftingJan 29, 2010

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.