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

Re: Add "clone" support to lntree

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Apr 16, 2005, 03:06 UTC
Message-ID
<Pine.LNX.4.21.0504152251300.30848-100000@iabervon.org>
In-Reply-To
<20050416024755.GX7417@pasky.ji.cz>
On Sat, 16 Apr 2005, Petr Baudis wrote:
Show 14 quoted lines
> Dear diary, on Sat, Apr 16, 2005 at 03:56:03AM CEST, I got a letter
> where Daniel Barkalow <barkalow@iabervon.org> told me that...
> > I often want to take a base tree, which I keep tracking some remote head,
> > and make a local working tree that starts from it. This makes "git ln -c
> > <dest>" give you a tree that you can just start working in and then diff
> > against the head you'd started from and send off.
> > 
> > Signed-Off-By: Daniel Barkalow <barkalow@iabervon.org>
> 
> I'm sorry but you are late, I added it about a hour and half ago or so.
> :-) Check git fork. (I *want* separate command than git lntree. In fact,
> I think I should make git lntree gitXlntree.sh instead, since it is
> really internal command for git-tools and the user should probably never
> need it for anything. git lntree is too lowlevel.)
Have you not pushed since? I don't see it.

I actually first made gitlntree.sh do the forking thing, because it didn't seem useful as is, until I noticed that merge was already using it internally.

Show 6 quoted lines
> Actually, I don't like the name at all, though. Some people may find
> pondering about names pointless, but when I'm going to type them in
> every day for the rest of my life, they better should not be stupid. ;-)
> 
> So, what are your clever ideas about git fork's proper name? Or should
> we leave it as is?

I think "fork" is as good as anything for describing the operation. I had thought about "clone" because it seemed to fill the role that "bk clone" had (although I never used BK, so I'm not sure). It doesn't seem useful to me to try cloning multiple remote repositories, since you'd get a copy of anything common from each; you just want to suck everything into the same .git/objects and split off working directories.

	-Daniel
*This .sig left intentionally blank*
Previous: David MansfieldNext: Petr Baudis
Message 26 of 29 in “Add "clone" support to lntree”
  1. Add "clone" support to lntreeDaniel Barkalow, Apr 16, 2005
  2. Petr BaudisApr 16, 2005
  3. Petr BaudisApr 16, 2005
  4. Linus TorvaldsApr 16, 2005
  5. Petr BaudisApr 16, 2005
  6. Daniel BarkalowApr 16, 2005
  7. Petr BaudisApr 16, 2005
  8. Daniel BarkalowApr 17, 2005
  9. Petr BaudisApr 19, 2005
  10. Change "pull" to _only_ download, and "git update"=pull+merge?David A. Wheeler, Apr 19, 2005
  11. David GreavesApr 19, 2005
  12. Petr BaudisApr 19, 2005
  13. Martin SchlemmerApr 19, 2005
  14. Petr BaudisApr 19, 2005
  15. Jon SeymourApr 19, 2005
  16. Martin SchlemmerApr 19, 2005
  17. Daniel BarkalowApr 19, 2005
  18. David A. WheelerApr 19, 2005
  19. Daniel BarkalowApr 19, 2005
  20. Ingo MolnarApr 20, 2005
  21. Petr BaudisApr 20, 2005
  22. Ingo MolnarApr 20, 2005
  23. Ingo MolnarApr 20, 2005
  24. Petr BaudisApr 20, 2005
  25. David MansfieldApr 20, 2005
  26. Daniel BarkalowApr 16, 2005
  27. Petr BaudisApr 16, 2005
  28. Daniel BarkalowApr 16, 2005
  29. Petr BaudisApr 16, 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.