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

Re: unseeking?

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Apr 24, 2005, 17:25 UTC
Message-ID
<Pine.LNX.4.21.0504241305370.30848-100000@iabervon.org>
In-Reply-To
<20050424160514.GI1507@pasky.ji.cz>
On Sun, 24 Apr 2005, Petr Baudis wrote:
Show 10 quoted lines
> Dear diary, on Sun, Apr 24, 2005 at 05:47:54PM CEST, I got a letter
> where Zack Brown <zbrown@tumblerings.org> told me that...
> > Hi,
> 
> Hi,
> > How can I seek back to the most recent state of the dir?
> 
> git seek, without any arguments.
> 
> Perhaps we should prohibit absence of arguments and add 'unseek'?

Have both; I think that it ought to accept anything where it's obvious what the user means.

Show 5 quoted lines
> Actually, this _would_ work:
> 
> 	git init ../mygitdir/.git
> 
> Then, you would need to git pull to get the latest changes.

It's worth pointing out that the reason for this (and why the rsync version below didn't work) is that the conventional URLs are for .git directories, not the directories that contain them: .../cogito/cogito.git mirrors a cogito/.git directory. Or, phrasing it the other way, when it's public, it's cogito.git; if it's in a working directory, it gets hidden by making it just .git.

> git fork seconddeveloper ../mygitdir

Doesn't that have to be from the first one to the second one (rather than the other way)?

> Git does not record renames, and neither does Cogito (for now).

And, in general, future history-browsing tools will work based on clever analysis of the files, not explicit information in the database. They ought to recognize when some content disappears from one place and something very similar appears elsewhere, regardless of whether it is a complete file or not.

I'm fairly certain that the most common rename-type events are moving code within a file, not renaming files, and these would be a major pain to get people to explicitly mark.

Show 5 quoted lines
> > 4) fork, seek, tag, and track are a little mysterious to me. I can guess at what
> > these things do in general, but the specifics are confusing, and the README is a
> > little vague.
> 
> Try head git*.sh. ;-)

Which is to say, there are useful comments at the beginnings of the scripts. I.e., you really want "head `which gitfork.sh`"

	-Daniel
*This .sig left intentionally blank*
Previous: Zack BrownNext: Zack Brown
Message 4 of 15 in “unseeking?”
  1. Zack BrownApr 24, 2005
  2. Petr BaudisApr 24, 2005
  3. Zack BrownApr 24, 2005
  4. Daniel BarkalowApr 24, 2005
  5. Zack BrownApr 24, 2005
  6. Daniel BarkalowApr 24, 2005
  7. Zack BrownApr 24, 2005
  8. Daniel BarkalowApr 24, 2005
  9. Zack BrownApr 25, 2005
  10. Daniel BarkalowApr 25, 2005
  11. Zack BrownApr 25, 2005
  12. Petr BaudisApr 26, 2005
  13. Zack BrownApr 26, 2005
  14. Petr BaudisApr 26, 2005
  15. Rename tracking, revisited (was: unseeking?)Kevin Smith, Apr 24, 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.