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

keeping track of where a patch begins

From
ERE R <pc88mxer@gmail.com>
Date
Oct 21, 2009, 14:45 UTC
Message-ID
<3a69fa7c0910210745r311cf18xf966f5c63650cde6@mail.gmail.com>
Hi,

We've started to use git at work. Developers create branches for their patches (which we call "tickets" because they are related to our ticketing system), and those branches are picked up by an integration team and merged together to form a release. Hopefully this is not too unconventional.

Ideally a developer will start their ticket branch from a previous release. However, occasionally a developer working on multiple tickets will forget to switch back to a release node when creating a new ticket branch. Then code from the first ticket inadvertently gets added to the second ticket, and this is a problem if integration decides to include the second ticket in the release but not the first.

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?

It seems that somehow the node that the patch begins at has to be either identified, marked or remembered, and it might have to done outside of git. Then the integration team or other tools can validate the starting node to ensure that it complies with the build process.

Thanks, ER

Next: Nicolas Pitre
Message 1 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.