From: Miles Bader <miles.bader@necel.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-reset.txt: Use uniform HEAD~N notation in all examples
Date: Mon, 03 Sep 2007 11:03:54 +0900 [thread overview]
Message-ID: <buolkbofqt1.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <veauqfu0.fsf@cante.net> (Jari Aalto's message of "Sat\, 01 Sep 2007 23\:40\:55 +0300")
Jari Aalto <jari.aalto@cante.net> writes:
> After all, the ^ very differento to what other SCM/VCSs use.
It's something I _constantly_ wished other SCM/VCSs had, as it's far,
far, more usable than the typical absolute rev numbers. It really
should be introduced as early as possible.
-Miles
--
Fast, small, soon; pick any 2.
prev parent reply other threads:[~2007-09-03 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 17:47 [PATCH] git-reset.txt: Use uniform HEAD~N notation in all examples Jari Aalto
2007-08-31 19:00 ` Junio C Hamano
2007-09-01 8:39 ` Jari Aalto
2007-09-01 9:40 ` Junio C Hamano
2007-09-01 15:01 ` Shawn Bohrer
2007-09-01 20:40 ` Jari Aalto
2007-09-03 2:03 ` Miles Bader [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=buolkbofqt1.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
--cc=miles@gnu.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