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

Re: How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?

From
Petr Baudis <pasky@suse.cz>
Date
Jul 28, 2005, 16:18 UTC
Message-ID
<20050728161815.GC17952@pasky.ji.cz>
In-Reply-To
<Pine.LNX.4.58.0507281747320.29968@wgmdd8.biozentrum.uni-wuerzburg.de>

Dear diary, on Thu, Jul 28, 2005 at 05:56:21PM CEST, I got a letter where Johannes Schindelin <Johannes.Schindelin@gmx.de> told me that...

> Hi,
Hello,
Show 18 quoted lines
> On Thu, 28 Jul 2005, Petr Baudis wrote:
> 
> > Dear diary, on Thu, Jul 28, 2005 at 03:07:01PM CEST, I got a letter
> > where Johannes Schindelin <Johannes.Schindelin@gmx.de> told me that...
> >
> > > On Thu, 28 Jul 2005, Petr Baudis wrote:
> > >
> > > > See above. I would much rather see more flexible git-send-pack. Junio,
> > > > what about changing its [heads]* parameter e.g. to
> > > > [remotehead[:localhead]]* ?
> > >
> > > IMHO this opens the door for shooting in your own foot. Isn't it much too
> > > easy to make a mistake with that syntax?
> >
> > What mistake?
> 
> To mix up different branches. With that syntax you can easily push changes
> onto the wrong head.

How? Only when you explicitly specify the remote head. When you're explicit, you ought to know what are you doing.

Show 5 quoted lines
> I might well be wrong here, but I think the most common usage for git-push
> is to update a public repository, which is done by one or just a few
> maintainer(s), in which case it is no problem to enforce
> localhead=remotehead. BTW, this whole multihead mess applies only to Jeffs
> anyway :-)

AFAIK the plan is to centralize all the kernel repositories to a single one. For that, developers would generally push into branches with name different that "master".

> I just do not see a high demand for mappings of remote and local HEAD
> names, but rather a high potential of making mistakes (after all, it is
> not the machine which makes mistakes, it's the human operator).

If you fear making mistakes, better use something which attempts to do some babysitting for you, like Cogito. ;-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox
Previous: Johannes SchindelinNext: Junio C Hamano
Message 7 of 41 in “How is working on arbitrary remote heads supposed to work in Cogito (+ PATCH)?”
  1. Josef WeidendorferJul 27, 2005
  2. Junio C HamanoJul 28, 2005
  3. Petr BaudisJul 28, 2005
  4. Johannes SchindelinJul 28, 2005
  5. Petr BaudisJul 28, 2005
  6. Johannes SchindelinJul 28, 2005
  7. Petr BaudisJul 28, 2005
  8. Junio C HamanoJul 28, 2005
  9. Johannes SchindelinJul 28, 2005
  10. Ryan AndersonJul 28, 2005
  11. Johannes SchindelinJul 28, 2005
  12. Petr BaudisJul 28, 2005
  13. Johannes SchindelinJul 28, 2005
  14. Matthias UrlichsJul 28, 2005
  15. Johannes SchindelinJul 28, 2005
  16. Petr BaudisJul 29, 2005
  17. Junio C HamanoJul 29, 2005
  18. Petr BaudisJul 29, 2005
  19. Junio C HamanoJul 29, 2005
  20. Petr BaudisJul 29, 2005
  21. Junio C HamanoJul 29, 2005
  22. Petr BaudisJul 29, 2005
  23. Johannes SchindelinJul 29, 2005
  24. Petr BaudisJul 29, 2005
  25. Johannes SchindelinJul 29, 2005
  26. Petr BaudisJul 29, 2005
  27. Junio C HamanoJul 30, 2005
  28. Matthias UrlichsJul 29, 2005
  29. Junio C HamanoJul 30, 2005
  30. Carl BaldwinAug 13, 2005
  31. Junio C HamanoAug 13, 2005
  32. Carl BaldwinAug 15, 2005
  33. Johannes SchindelinAug 15, 2005
  34. Josef WeidendorferJul 29, 2005
  35. Matthias UrlichsJul 28, 2005
  36. Petr BaudisJul 29, 2005
  37. Josef WeidendorferJul 28, 2005
  38. Unnamed branchesPetr Baudis, Jul 28, 2005
  39. Junio C HamanoJul 28, 2005
  40. Petr BaudisJul 28, 2005
  41. Petr BaudisJul 28, 2005

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.