From: Jakub Narebski <jnareb@gmail.com>
To: Brendan Cully <brendan@kublai.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
mercurial@selenic.com, git@vger.kernel.org
Subject: Re: newbie questions about git design and features (some wrt hg)
Date: Fri, 2 Feb 2007 21:15:31 +0100 [thread overview]
Message-ID: <200702022115.31571.jnareb@gmail.com> (raw)
In-Reply-To: <20070202195504.GC7963@ventoux.cs.ubc.ca>
Brendan Cully wrote:
> Just because a tag is created at a different time than the revision it
> tags, that doesn't mean that it is ahistorical. It's still interesting
> to know what the state of the repository was when the tag was
> created.
I think not. Why would one want to know what was the state of the
repository when the tag (perhaps to some historical, old commit)
was created?
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-02-02 20:14 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 16:20 newbie questions about git design and features (some wrt hg) Mike Coleman
2007-01-30 16:41 ` Johannes Schindelin
2007-01-30 16:55 ` Shawn O. Pearce
2007-01-31 1:55 ` Theodore Tso
2007-01-31 10:56 ` Jakub Narebski
2007-01-31 20:01 ` Junio C Hamano
2007-01-31 22:25 ` Matt Mackall
2007-01-31 23:58 ` Jakub Narebski
2007-02-01 0:34 ` Matt Mackall
2007-02-01 0:57 ` Jakub Narebski
2007-02-01 7:59 ` Simon 'corecode' Schubert
2007-02-01 10:09 ` Johannes Schindelin
2007-02-01 10:15 ` Simon 'corecode' Schubert
2007-02-01 10:49 ` Johannes Schindelin
2007-02-01 16:28 ` Linus Torvalds
2007-02-01 19:36 ` Eric Wong
2007-02-01 21:13 ` Linus Torvalds
2007-02-02 9:55 ` Jakub Narebski
2007-02-02 13:51 ` Simon 'corecode' Schubert
2007-02-02 14:23 ` Jakub Narebski
2007-02-02 15:02 ` Shawn O. Pearce
2007-02-02 15:38 ` Mark Wooding
2007-02-02 16:09 ` Jakub Narebski
2007-02-02 16:42 ` Linus Torvalds
2007-02-02 16:59 ` Jakub Narebski
2007-02-02 17:11 ` Linus Torvalds
2007-02-02 17:59 ` Brendan Cully
2007-02-02 18:19 ` Jakub Narebski
2007-02-02 19:28 ` Brendan Cully
2007-02-02 18:27 ` Giorgos Keramidas
2007-02-02 19:01 ` Linus Torvalds
2007-02-03 21:20 ` Giorgos Keramidas
2007-02-03 21:37 ` Matthias Kestenholz
2007-02-03 21:41 ` Linus Torvalds
2007-02-03 21:45 ` Jakub Narebski
2007-02-02 18:32 ` Linus Torvalds
2007-02-02 19:26 ` Brendan Cully
2007-02-02 19:42 ` Linus Torvalds
2007-02-02 19:55 ` Brendan Cully
2007-02-02 20:15 ` Jakub Narebski [this message]
2007-02-02 20:21 ` Linus Torvalds
2007-02-02 16:03 ` Matt Mackall
2007-02-02 17:18 ` Jakub Narebski
2007-02-02 17:37 ` Matt Mackall
2007-02-02 18:44 ` Jakub Narebski
2007-02-02 19:56 ` Jakub Narebski
2007-02-03 20:06 ` Brendan Cully
2007-02-03 20:55 ` Jakub Narebski
2007-02-03 21:00 ` Jakub Narebski
2007-01-30 17:44 ` Jakub Narebski
2007-01-30 18:06 ` Linus Torvalds
2007-01-30 19:37 ` Linus Torvalds
2007-01-30 18:11 ` Junio C Hamano
2007-01-31 3:38 ` Mike Coleman
2007-01-31 4:35 ` Linus Torvalds
2007-01-31 4:57 ` Junio C Hamano
2007-01-31 16:22 ` Linus Torvalds
2007-01-31 16:41 ` Johannes Schindelin
2007-01-31 7:11 ` Mike Coleman
2007-01-31 15:03 ` Nicolas Pitre
2007-01-31 16:58 ` Mike Coleman
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=200702022115.31571.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=brendan@kublai.com \
--cc=git@vger.kernel.org \
--cc=mercurial@selenic.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.