git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Zack Brown <zbrown@tumblerings.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: seek request
Date: Thu, 26 May 2005 10:29:41 +0200	[thread overview]
Message-ID: <20050526082941.GC22262@pasky.ji.cz> (raw)
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

      reply	other threads:[~2005-05-26  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-22  7:11 seek request Zack Brown
2005-05-26  8:29 ` Petr Baudis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050526082941.GC22262@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=zbrown@tumblerings.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).