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

Re: repo.or.cz wishes?

From
Petr Baudis <pasky@suse.cz>
Date
Aug 29, 2007, 09:54 UTC
Message-ID
<20070829095400.GF1219@pasky.or.cz>
In-Reply-To
<20070829042005.GT18160@spearce.org>
On Wed, Aug 29, 2007 at 06:20:05AM CEST, Shawn O. Pearce wrote:
Show 27 quoted lines
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Tue, 28 Aug 2007, Theodore Tso wrote:
> > > On Tue, Aug 28, 2007 at 12:10:59AM -0400, Shawn O. Pearce wrote:
> > > > At day-job I have a hard rule that you cannot even push into an A, let 
> > > > alone rewind a branch in it or delete a branch from it.
> > > 
> > > Why don't you even allow people to push into A?  That should be safe....
> > 
> > Nope:
> > 
> > for b in $(git ls-remote /that/other/repo | sed "s/^[^ ]* //")
> > do
> > 	git push /that/other/repo :$b
> > done
> 
> Well, at day-job I use contrib/hooks/update-paranoid to deny all
> push access into my A's (/that/other/repo).  But that could just
> as easily be configured to allow branch creation and branch update
> (fast-forward) but no rewind or delete.
> 
> When I symlink A's refs into B I also don't allow B to update,
> create, rewind or delete the symlinked refs via push.  This way
> you can't do something weird to A like upload new objects into B's
> ODB but then change A's refs to point to objects that A's own ODB
> doesn't have.
> 
> Hmm, I wonder of Pasky handles that correctly on repo.or.cz...

I don't handle it at all, but if you don't have permissions to modify A you simply won't be able to do anything weird to A. If you have the permissions, I'm still not sure if Git will keep symlinked refs over ref updates; if so, hey, you had the permissions for A and it's your reponsibility if you screw up.

-- 
				Petr "Pasky" Baudis
Early to rise and early to bed makes a male healthy and wealthy and dead.
                -- James Thurber
Previous: Jakub NarebskiNext: Petr Baudis
Message 23 of 28 in “repo.or.cz wishes?”
  1. Petr BaudisAug 26, 2007
  2. Sven VerdoolaegeAug 27, 2007
  3. Petr BaudisAug 27, 2007
  4. Linus TorvaldsAug 27, 2007
  5. Junio C HamanoAug 27, 2007
  6. Matthieu MoyAug 27, 2007
  7. Martin MaresAug 27, 2007
  8. Jing XueAug 27, 2007
  9. Linus TorvaldsAug 27, 2007
  10. Sam VilainAug 27, 2007
  11. Linus TorvaldsAug 27, 2007
  12. Jakub NarebskiAug 27, 2007
  13. Linus TorvaldsAug 27, 2007
  14. Sam VilainAug 27, 2007
  15. Linus TorvaldsAug 27, 2007
  16. Jakub NarebskiAug 27, 2007
  17. Jakub NarebskiAug 27, 2007
  18. Sam VilainAug 27, 2007
  19. Johannes SchindelinAug 27, 2007
  20. Uwe Kleine-KönigAug 27, 2007
  21. Sven VerdoolaegeAug 29, 2007
  22. Jakub NarebskiAug 29, 2007
  23. Petr BaudisAug 29, 2007
  24. Petr BaudisAug 29, 2007
  25. Theodore TsoAug 29, 2007
  26. Shawn O. PearceAug 31, 2007
  27. Linus TorvaldsAug 29, 2007
  28. Shawn O. PearceSep 1, 2007

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.