From: Wink Saville <wink@saville.com>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org, zbrown@tumblerings.org
Subject: Re: README rewrite
Date: Sun, 15 May 2005 08:30:56 -0700 [thread overview]
Message-ID: <42876B30.1070404@saville.com> (raw)
In-Reply-To: <4286F146.2090302@saville.com>
Wink Saville wrote:
> Zack Brown wrote:
>
> > Hi Petr,
> >
<snip>
> Actually looking in the repository I see that "origin" appears to be a
> "branch" not a revision, what is the relationship between a branch, tag
> and revision's? I have some experience with subversion and in subversion
> they are actually all the same, simply the state of a "sub-tree" within
> the repository at a particular "time". That time is defined by the
> repositories current revison number which is incremented after each
> succesful commit to the repository.
>
Zack,
I patched the README by hand this morning and read the explanation on cg-tag and it
appears branches, tags and revisions are synonymous, please correct me if I'm wrong.
Is there a way to use time or relative values (HEAD-1) as "revision" parameters, it would
be nice if its not already there.
Again, thanks for the update adds very useful information!
Wink
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.10 - Release Date: 5/13/2005
next prev parent reply other threads:[~2005-05-15 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 4:42 README rewrite Zack Brown
2005-05-15 4:49 ` Zack Brown
2005-05-15 6:50 ` Wink Saville
2005-05-15 15:17 ` Zack Brown
2005-05-15 15:30 ` Wink Saville [this message]
2005-05-15 15:40 ` Zack Brown
2005-05-15 15:53 ` Zack Brown
2005-05-15 17:28 ` Petr Baudis
2005-05-16 15:16 ` Zack Brown
2005-05-18 21:42 ` Petr Baudis
2005-05-15 17:33 ` Matthias Urlichs
2005-05-18 22:27 ` Petr Baudis
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=42876B30.1070404@saville.com \
--to=wink@saville.com \
--cc=git@vger.kernel.org \
--cc=zbrown@tumblerings.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;
as well as URLs for NNTP newsgroup(s).