Re: unseeking?

From: Zack Brown <zbrown@tumblerings.org>
Date: Apr 24, 2005, 16:29 UTC
Message-ID: <20050424162943.GB11094@tumblerings.org>
In-Reply-To: <20050424160514.GI1507@pasky.ji.cz>

On Sun, Apr 24, 2005 at 06:05:14PM +0200, Petr Baudis wrote:

Show 21 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,
> 
> > I've been pulling cogito and the kernel, and just fumbling around trying to
> > learn the tool. My latest cogito is version 0.7, tracking
> > 
> > pasky   rsync://rsync.kernel.org/pub/scm/cogito/cogito.git
> > linus   rsync://www.kernel.org/pub/linux/kernel/people/torvalds/git.git
> > 
> > I have many questions.
> > 
> > 1) I saw some discussion of 'seek' as a way to get to an earlier version of a
> > tree; so I tried it on my own test directory. I 'seek'ed to the first patch, and
> > it worked - but now all I have is that very early version of my test directory.
> > All subsequent changes are apparently gone. How can I seek back to the most
> > recent state of the dir?
> 
> git seek, without any arguments.

This didn't work. I did a 'git seek' and I still see only the early version of my directory. However, see the next point for more on this.

Show 17 quoted lines

> 
> Perhaps we should prohibit absence of arguments and add 'unseek'?
> 
> > 2) How can I 'check out' my local repository? i.e. I want to pretend to be
> > two developers, one of whom wants to grab a copy of the project leader's work. I
> > tried things like:
> > 
> > mkdir mygitdir2
> > git init ../mygitdir
> > 
> > where mydir is my test git repository. This didn't work. I tried rephrasing the
> 
> Actually, this _would_ work:
> 
> 	git init ../mygitdir/.git
> 
> Then, you would need to git pull to get the latest changes.

OK, I did 'git init ../mygitdir/.git', and it worked, I didn't even need to do a pull. It's a little unintuitive that I would have to specifically identify the .git subdirectory in that command. But it worked.

So, regarding my first point. When I did the init from the original repo, the new repo got the latest snapshot of the tree. So I did a 'git log' in the new directory to obtain the latest d394a1e71504c6f032a484bbd5e8ecbe4c3de05e thingy.

Then I went back to my main directory (the one I'd seeked back to the beginning), and did

git seek d394a1e71504c6f032a484bbd5e8ecbe4c3de05e

but it didn't work. The directory is still stuck at the beginning of its history.

Show 14 quoted lines

> 
> > command with an rsync url:
> > 
> > git init rsync://home/zbrown/site/gitstuff/mygitdir
> > 
> > but that didn't work either. It just said:
> > 
> > defaulting to local storage area
> > rsync: getaddrinfo: home 873: Name or service not known
> > rsync error: error in socket IO (code 10) at clientserver.c(94)
> > gitpull.sh: unable to get the head pointer of branch master
> > gitinit.sh: pull failed
> 
> git fork seconddeveloper ../mygitdir

Can you say what this does? Is it the same as the init+pull you described above?

Hmm... I tried it, and got:

09:24:06 [zbrown] ~/site/gitstuff/mygit3$ git fork seconddeveloper ../mygitdir cat: .git/HEAD: No such file or directory Invalid id: grep: .git/remotes: No such file or directory gitfork.sh: ../mygitdir already exists 09:24:07 [zbrown] ~/site/gitstuff/mygit3$

Show 7 quoted lines

> 
> > 3) How can I do a rename with cogito? There doesn't seem to be a rename command,
> > and if I manually do a mv and 'git add', I can commit the result, but what
> > actually happened? Did I really do a rename? Is the file's history preserved?
> > How can I verify these things?
> 
> Git does not record renames, and neither does Cogito (for now).

OK

Show 6 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. ;-)

heh. This is not more clear ;-)

Show 16 quoted lines

> 
> > 5) I'm a little confused about how to use a git repository to follow along with
> > a project. I have no problem pulling the latest version, but I'm interested in
> > generating changelogs for specific releases like 2.6.12-rc3. How can I
> > 
> >    a) identify the proper 'c83b95297c2a6336c2007548f909769e0862b509' string that
> >    represents the release I'm interested in
> 
> Assuming that it is tagged, just do
> 
> 	commit-id linux-2.6.12-rc3
> 
> or whatever the tag name is. From Cogito perspective, you can use the
> symbolic name anywhere you would use the proper string.
> 
> There is also tree-id and parent-id, with same usage.

OK, I still have questions on this, but I see tagging is getting some heavy work today. I think I'll wait till that shakes out.

Show 10 quoted lines

> 
> >    b) generate the changelog between that version and the previous one,
> >    once I've solved (a)
> 
> 	git log previous that
> 
> Any ideas how to improve the user interface further are deeply
> appreciated. (However please note that it is going to undergo a big
> change in an hour or two, so you might want to postpone them until
> that.)

Be well, Zack

Show 9 quoted lines

> 
> -- 
> 				Petr "Pasky" Baudis
> Stuff: http://pasky.or.cz/
> C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Zack Brown