# seek request

2 messages from 2005-05-22 to 2005-05-26. Participants: Zack Brown, Petr Baudis.
Thread: https://gitlist.dev/t/689

## Zack Brown, 2005-05-22 07:11

Subject: seek request
Message-ID: <20050522071106.GA8060@tumblerings.org>
URL: https://gitlist.dev/e/20050522071106.GA8060%40tumblerings.org

```
Hi folks,

In Cogito, it would be nice to have a

cg-seek +

that would seek to the next archive state. This way, I could start off seeking
back to the beginning of an archive, and quickly step forward, looking at files
as I went, to the present.

A corresponding
cg-seek -
would go the reverse direction, back toward the beginning of a project.

I'm not sure how useful this would be for actual source code - I suspect any
benefit would be minimal - but the benefit for documentation and text files,
where the only way to test improvements is to read them by eye, would be
significant.

Be well,
Zack

-- 
Zack Brown

```

## Petr Baudis, 2005-05-26 08:29

Subject: Re: seek request
Message-ID: <20050526082941.GC22262@pasky.ji.cz>
URL: https://gitlist.dev/e/20050526082941.GC22262%40pasky.ji.cz
In-Reply-To: <20050522071106.GA8060@tumblerings.org>

```
Dear diary, on Sun, May 22, 2005 at 09:11:06AM CEST, I got a letter
where Zack Brown <zbrown@tumblerings.org> told me that...
> Hi folks,
> 
> In Cogito, it would be nice to have a
> 
> cg-seek +
> 
> that would seek to the next archive state. This way, I could start off seeking
> back to the beginning of an archive, and quickly step forward, looking at files
> as I went, to the present.
> 
> A corresponding
> cg-seek -
> would go the reverse direction, back toward the beginning of a project.
> 
> I'm not sure how useful this would be for actual source code - I suspect any
> benefit would be minimal - but the benefit for documentation and text files,
> where the only way to test improvements is to read them by eye, would be
> significant.

Well, and what if the commit has multiple parents? Or - even much more
interestingly - multiple children?

If we keep applying the first parent rule, we could just traverse the
graph from heads/master to HEAD following this rule, and then just take
a step back to where we came from for cg-seek +. It wouldn't be exactly
cheap, but it'd probably work.

Patch welcomed. ;-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

```
