From: Theodore Ts'o <tytso@mit.edu>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Konstantin Khomoutov <kostix+git@007spb.ru>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Specifying N revisions after the initial commit
Date: Tue, 22 Sep 2015 16:40:00 -0400 [thread overview]
Message-ID: <20150922204000.GC3318@thunk.org> (raw)
In-Reply-To: <CA+5PVA6zUXGs2R-MOoj5sBxwUqM7HP=tx-0WZJzPf71MsjH9MA@mail.gmail.com>
On Tue, Sep 22, 2015 at 04:11:23PM -0400, Josh Boyer wrote:
> Oh, context would help, yes. In the case of the tree I'm parsing, I
> know for a fact that the commit history is entirely linear and will
> (should) always remain so. E.g.
>
> A - B - C - D - E - F ... {N}
>
> So yes, finding e.g. the second commit after the root is complicated
> for something resembling anything like a typical git repo, but this
> isn't like that. In other words, I can cheat. Or at least I'm pretty
> sure I can cheat :).
I'd suggest making your script makes sure "git rev-list --merges A..N"
doesn't output any commits, so you know for sure that the commit
history is linear. That way you'll be certain that you can cheat. :-)
- Ted
next prev parent reply other threads:[~2015-09-22 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 18:32 Specifying N revisions after the initial commit Josh Boyer
2015-09-22 18:40 ` Konstantin Khomoutov
2015-09-22 19:10 ` Josh Boyer
2015-09-22 19:55 ` Junio C Hamano
2015-09-22 20:11 ` Josh Boyer
2015-09-22 20:40 ` Theodore Ts'o [this message]
2015-09-22 20:42 ` Junio C Hamano
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=20150922204000.GC3318@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jwboyer@gmail.com \
--cc=kostix+git@007spb.ru \
/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