From: Yakup Akbay <yakbay@ubicom.com>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org
Subject: Re: Pro Git Book -- Git
Date: Tue, 28 Jul 2009 14:32:25 +0300 [thread overview]
Message-ID: <4A6EE1C9.8090701@ubicom.com> (raw)
> Hey all,
>
> Just a heads up - I've been working on a book on Git being published
> by Apress called "Pro Git", which is being licensed under a CC 3.0
> license and as I've just finished some of the final reviews, I've put
> the entire content of the book online at:
>
> http://progit.org
>
> It should be shipping at the end of August, I think, but I just wanted
> to let people know that there is another resource out there to help
> learn Git. This one was actually technically edited by Shawn, too, so
> hopefully not too many serious errors of mine got through.
>
> I've added a link to it on http://git-scm.com under the Books section,
> in case you want to point any newbies there. Hope this helps take
> some teaching load off some of your plates.
>
> Thanks,
> Scott
Great!
BTW, I've had the chance to read the last section (Git Internals) and there's one sentence, which I'm not sure about the meaning.
The last paragraph in http://progit.org/book/ch9-3.html states:
> Remote references differ from branches (|refs/heads| references)
> mainly in that they can’t be checked out. Git moves them around as
> bookmarks to the last known state of where those branches were on
> those servers.
Is this true? If I do `git checkout <remote>/<branch>` then I can checkout the tree, which is referenced by the 'remote reference'.
Or am I misunderstanding the sentence? What is meant by 'remote reference' and by this sentence?
P.s. I just have subscribed to the maillist but not approved yet. So, it might not go to the right place. Sorry, if this email does not appear under the correct thread.
Regards,
Yakup
reply other threads:[~2009-07-28 11:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A6EE1C9.8090701@ubicom.com \
--to=yakbay@ubicom.com \
--cc=d411cc4a0907271056x458d7b15lc1b2868a46884175@mail.gmail.com \
--cc=git@vger.kernel.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).