From: Jakub Narebski <jnareb@gmail•com>
To: Andreas Schwab <schwab@linux-m68k•org>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>,
jpaugh@gmx•us, git@vger•kernel.org
Subject: Re: Specifying revisions in the future
Date: Sun, 05 Feb 2012 13:57:55 -0800 (PST) [thread overview]
Message-ID: <m3ehu9kknw.fsf@localhost.localdomain> (raw)
In-Reply-To: <m21uq9x8q2.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k•org> writes:
> Matthieu Moy <Matthieu.Moy@grenoble-inp•fr> writes:
>
> > "the successor of <commit>", OTOH, is not well defined, since there can
> > be several successors, and one can't order them reliably (you can't
> > really know the set of successors, because they can exist in different
> > repositories).
>
> Yet it would be nice to have a concise notation for "the nth successor
> of <commit> towards <commit>" (using --first-parent ordering when
> ambiguous).
First, "the nth successor"... from which refs? Commit objects have
pointers in one direction only, from commit to its ancestors (earlier
commits).
Second, `--first-parent' won't help here. Take for example the
following situation:
---X<---*<---.<---A
\
\--.<---B
X+3 is A or B? Note that pointers point _to_ '*' commit, so there is
not first or second here - no natural ordering like in the case of
commit parents.
--
Jakub Narebski
next prev parent reply other threads:[~2012-02-05 21:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 15:58 Specifying revisions in the future jpaugh
2012-02-05 2:44 ` Jakub Narebski
[not found] ` <4F2DEF89.4030302@gmx.us>
2012-02-05 3:07 ` Jakub Narebski
2012-02-05 20:18 ` Matthieu Moy
2012-02-05 21:37 ` Andreas Schwab
2012-02-05 21:57 ` Jakub Narebski [this message]
2012-02-05 22:15 ` Andreas Schwab
2012-02-05 22:24 ` Jakub Narebski
2012-02-05 22:58 ` Andreas Schwab
2012-02-05 22:58 ` Philip Oakley
2012-02-05 23:08 ` Andreas Schwab
2012-02-06 4:28 ` Miles Bader
2012-02-07 21:25 ` Jonathan Paugh
2012-02-06 11:43 ` Matthieu Moy
2012-02-06 12:27 ` Andreas Schwab
2012-02-05 21:59 ` 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=m3ehu9kknw.fsf@localhost.localdomain \
--to=jnareb@gmail$(echo .)com \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=jpaugh@gmx$(echo .)us \
--cc=schwab@linux-m68k$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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