Git development
 help / color / mirror / Atom feed
From: Adam Piatyszek <ediap@users.sourceforge.net>
To: Rafa? Mu?y?o <galtgendo@o2.pl>
Cc: git@vger.kernel.org
Subject: Re: Git vs svn. Is ... possible ?
Date: Fri, 28 Mar 2008 14:36:25 +0100	[thread overview]
Message-ID: <47ECF459.2040500@users.sourceforge.net> (raw)
In-Reply-To: <20080328132438.GA32646@blackspire>

Hi Rafał,

* Rafa? Mu?y?o [28 III 2008 14:24]:
> Well, the actual question is:
> In svn I can do a remote diff (diff between two remote revisions) without
> having to do a checkout, is this possible for git ?

The question makes no sense to me. Git by design is a distributed SCM 
tool, so there is no such thing like "remote revisions". You can have 
tracking branches (clones) of some remote repositories, but all the 
commits on such branches are also stored locally. So you have full 
access to them, even without a permanent connection to such remote 
repositories.

And answering to the second part of your question: Yes, you can do "git 
diff" operation between any of the commits in the repository you are 
working with. No need to checkout before. You can perform "git diff" 
even on a bare repository without the working three.

Please refer to "man git-diff" for more info.

BR,
/Adam


PS. The encoding you used for your message is not playing well with the 
Polish accented characters in your name ;)

-- 
.:.  Adam Piatyszek (ediap)  .:.....................................:.
.:.  ediap@users.sourceforge.net  .:................................:.

  reply	other threads:[~2008-03-28 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 13:24 Git vs svn. Is ... possible ? Rafał Mużyło
2008-03-28 13:36 ` Adam Piatyszek [this message]
2008-03-28 14:31   ` Theodore Tso
2008-03-28 14:09 ` Bill Lear
2008-03-31 15:41 ` John Goerzen

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=47ECF459.2040500@users.sourceforge.net \
    --to=ediap@users.sourceforge.net \
    --cc=galtgendo@o2.pl \
    --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