git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: "Joshua Ball" <sciolizer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: svn user trying to recover from brain damage
Date: Wed, 09 May 2007 09:02:29 -0700	[thread overview]
Message-ID: <874pmmkmsq.wl%cworth@cworth.org> (raw)
In-Reply-To: <92fdc3450705090830t64c8f5b9r4af277807dfe834d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]

On Wed, 9 May 2007 10:30:18 -0500, "Joshua Ball" wrote:
> Is there a difference between HEAD and the working tree?

Yes. HEAD is a pointer to committed state. HEAD is an alias for the
current branch.

> Does HEAD change when I cg-switch/git-checkout?

Yes.

> What is an object?

It's a low-level aspect of git's unified storage model. The various
object types, (blob, tree, commit, tag),  are defined quite clearly in
the documentation.

> What the heck is a branch?

Simply a pointer to the DAG that moves as new commits are created
while "on" that branch.

> More on branches: The wiki says that a group of commits linked
> together form a DAG.

Yes.

>                      Does that mean every fork/clone/branch-create
> possibly doubles the number of branches.

No. Creating a new branch simply references some existing commit in
the DAG already.

>                                           So if I fork and then
> remerge, do I have two branches?
>
> A -> B -> D
> A -> C -> D

No. If you merged you would have history that looks like this:

 /-> B -\
A        D
 \-> C -/

> Is there a standard revision notation?

Yes. See the documentation for git-rev-parse and the section on
specifing revisions, (hint: when you run a command like "git log" and
see long sequence of hex characters, you can use those (or abbreviated
versions of those) to name revisons). You can also do many other
things as described in the documentation.

[Beyond this point you bring in too many svn misconceptions to make
the questions easy to answer.]

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-09 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 15:30 svn user trying to recover from brain damage Joshua Ball
2007-05-09 16:02 ` Carl Worth [this message]
2007-05-09 16:12   ` Karl Hasselström
2007-05-09 16:22 ` Petr Baudis
2007-05-09 20:16   ` Jan Hudec
2007-05-09 16:57 ` Linus Torvalds
2007-05-09 17:43 ` J. Bruce Fields
2007-05-11 17:29 ` Jakub Narebski

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874pmmkmsq.wl%cworth@cworth.org \
    --to=cworth@cworth.org \
    --cc=git@vger.kernel.org \
    --cc=sciolizer@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).