From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: jpaugh@gmx•us
Cc: git@vger•kernel.org
Subject: Re: Specifying revisions in the future
Date: Sun, 05 Feb 2012 21:18:14 +0100 [thread overview]
Message-ID: <vpqipjlf309.fsf@bauges.imag.fr> (raw)
In-Reply-To: <jgjkk0$qrg$1@dough.gmane.org> (jpaugh@gmx.us's message of "Sat, 04 Feb 2012 10:58:55 -0500")
jpaugh@gmx•us writes:
> Hello.
>
> Is it possible to specify revisions in the future?
You mean, the opposite of <commit>^ or <commit>~n?
AFAIK, there isn't, and there's a good reason for that: <commit>^ is
well-defined, it's the first parent of <commit>, and it won't change
unless one rewrites this commit.
"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).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-02-05 20:18 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 [this message]
2012-02-05 21:37 ` Andreas Schwab
2012-02-05 21:57 ` Jakub Narebski
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=vpqipjlf309.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=jpaugh@gmx$(echo .)us \
/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