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

Re: Tracability in git commits

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 29, 2008, 16:08 UTC
Message-ID
<alpine.DEB.1.00.0804291707210.27457@eeepc-johanness>
In-Reply-To
<1209473739.5642.31.camel@dax.rpnet.com>
Hi,
On Tue, 29 Apr 2008, Richard Purdie wrote:
> I've been wondering about whether its possible to provide some degree of 
> traceability of commits to a shared git repository. The potential 
> nightmare scenario is one developer making a commit pretending to be 
> someone else.

You will probably not like my answer: if you do not trust your fellow developers, do not use a shared repository. Use clones (such as Linux' many different repositories on kernel.org) instead.

Ciao, Dscho

Previous: Richard PurdieNext: Junio C Hamano
Message 2 of 15 in “Tracability in git commits”
  1. Richard PurdieApr 29, 2008
  2. Johannes SchindelinApr 29, 2008
  3. Junio C HamanoApr 29, 2008
  4. Richard PurdieApr 29, 2008
  5. Shawn O. PearceApr 30, 2008
  6. Ping YinApr 30, 2008
  7. Miklos VajnaApr 30, 2008
  8. Shawn O. PearceMay 1, 2008
  9. Ping YinMay 1, 2008
  10. Jakub NarebskiApr 30, 2008
  11. Richard PurdieApr 30, 2008
  12. Martin LanghoffMay 1, 2008
  13. Martin LanghoffMay 1, 2008
  14. Junio C HamanoMay 1, 2008
  15. Martin LanghoffMay 1, 2008

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.