From: Jonathan Nieder <jrnieder@gmail.com>
To: Alexey Shumkin <zapped@mail.ru>
Cc: git@vger.kernel.org, Akash <bcakashguru@gmail.com>
Subject: Re: git fetch,git merge and git rebase
Date: Thu, 10 Feb 2011 02:22:18 -0600 [thread overview]
Message-ID: <20110210082218.GA5997@elie> (raw)
In-Reply-To: <loom.20110210T082201-996@post.gmane.org>
Alexey Shumkin wrote:
> Akash writes:
>> I am new to git .Can someone explain in simple terms what git fetch,git
>> merge and git rebase do?..I tried googling but was very confused after going
>> thro it.
>>
>> Also, can someone prescribe a link which explains git in detail right from
>> scratch.
>
> RFTM, with all respect ))
> http://progit.org/book/
More hints:
- "man git" (or "git help git") has some hints to get started:
. a tutorial
. a list of "everyday git" commands to get going
. a short article on centralized, cvs-style workflow
. a user's manual
- when anything is unclear in those documents, I will be very happy
to learn about it (so cc me in that case :)). Please be specific
as possible about what is confusing.
- people on this mailing list and the #git channel on freenode are
generally happy to help if you are trying to do something
specific (or have some other specific question).
- there's much material on the web in addition to what's mentioned
above. For example the old git crash course for svn users at
http://git.or.cz/course/svn.html taught me a lot about both git and
svn. Theoretically, good material from a variety of sources can
gradually flow into the user's manual and reference manual pages,
though actual practice does not always match that theory.
Good luck.
Kind regards,
Jonathan
next prev parent reply other threads:[~2011-02-10 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 5:29 git fetch,git merge and git rebase Akash
2011-02-10 7:22 ` Alexey Shumkin
2011-02-10 8:22 ` Jonathan Nieder [this message]
2011-02-11 6:59 ` Akash
2011-02-10 7:25 ` Alexey Shumkin
2011-02-10 20:00 ` Neal Kreitzinger
2011-02-10 22:21 ` Neal Kreitzinger
2011-02-10 23:03 ` Jeff King
2011-02-11 7:00 ` Akash
2011-02-11 12:32 ` Felipe Contreras
2011-02-11 17:13 ` Neal Kreitzinger
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=20110210082218.GA5997@elie \
--to=jrnieder@gmail.com \
--cc=bcakashguru@gmail.com \
--cc=git@vger.kernel.org \
--cc=zapped@mail.ru \
/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).