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

Re: Disallow amending published commits?

From
JPJames Pickens <jepicken@gmail.com>
Date
Mar 21, 2009, 22:49 UTC
Message-ID
<885649360903211549h751c19e6sbaa0e07a14413d19@mail.gmail.com>
In-Reply-To
<eaa105840903211146s4ff398e3qa8b570a8d29a83f4@mail.gmail.com>
[Resend since I forgot to cc the list]
On Sat, Mar 21, 2009, Peter Harris <git@peter.is-a-geek.org> wrote:
Show 7 quoted lines
> An amended commit will have a new SHA1, and therefore git will treat
> it as an entirely different commit. Trying to push an amended history
> is 'non fast forward' in git terminology, since it involves a rewind
> of existing history.
>
> Set receive.denyNonFastForwards if you don't want people to be able to
> amend (or otherwise rewind) published history.

Thanks, but unfortunately that won't work in our workflow. Users never push their changes; instead, they do a turnin to a continuous integration server. The server clones the central repo, pulls their changes into the clone, builds and tests it, then pushes to the central repo if it passes the tests. So integration happens via 'pull' instead of 'push'.

We can't force the pulls to be fast forward only, because we need to allow turnins from multiple users to be built and tested in parallel, without requiring users to pull from each other or otherwise coordinate their turnins.

James
Previous: Peter HarrisNext: Peter Harris
Message 3 of 9 in “Disallow amending published commits?”
  1. James PickensMar 21, 2009
  2. Peter HarrisMar 21, 2009
  3. James PickensMar 21, 2009
  4. Peter HarrisMar 22, 2009
  5. Peter HarrisMar 22, 2009
  6. James PickensMar 22, 2009
  7. Peter HarrisMar 22, 2009
  8. Nicolas SebrechtMar 22, 2009
  9. Jeff KingMar 22, 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.