From: Sergei Organov <osv@javad.com>
To: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
Cc: "Nicolas Pitre" <nico@cam.org>,
"Matthieu Moy" <Matthieu.Moy@imag.fr>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git fetch: where are the downloaded objects stored?
Date: Mon, 03 Mar 2008 20:18:45 +0300 [thread overview]
Message-ID: <87hcfnu3nu.fsf@osv.gnss.ru> (raw)
In-Reply-To: <4d8e3fd30803030851n498953c4u7e7a109b91b9da11@mail.gmail.com> (Paolo Ciarrocchi's message of "Mon\, 3 Mar 2008 17\:51\:03 +0100")
"Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com> writes:
> On Mon, Mar 3, 2008 at 5:29 PM, Nicolas Pitre <nico@cam.org> wrote:
>> On Mon, 3 Mar 2008, Paolo Ciarrocchi wrote:
>>
>> > On Mon, Mar 3, 2008 at 4:21 PM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
[...]
>> > How can I look to what I just downloaded?
>> > Should I simply do a git diff?
>>
>> If you have reflog enabled (it should be by default) then a good thing
>> to remember is the @{1} notation. For example, if the fetch updated the
>> origin/master branch, then origin/master@{1} is what your origin/master
>> was before being updated. To see the difference between the previous
>> and the current state of origin/master, you can do:
>>
>> git diff origin/master@{1}..origin/master
>>
>> Or to see the list of new commits:
>>
>> git log origin/master@{1}..origin/master
>>
>> git log -p origin/master@{1}..origin/master
>>
>> Etc.
>
> Very nice, I didn't find in the documentation.
> I'll read again the documents and if needed, I'll propose some new text.
>
>> This notation is a bit obnoxious and the re were suggestions about
>> addind the equivalent origin/master@{1..} but that didn't materialize
>> yet.
>
> Mybe it's just me but wouldn't be very nice to have a simple command
> to look at what data have been used for updating the currente branch?
> i.e.
> git fetch
> git diff -- fetch (which is an alias of git diff
> origin/master@{1}..origin/master)
>
> And how about a repository which have reflogs disabled?
I'm also a newbie, and I think you are on a wrong road. Usually it's not
that interesting what was downloaded. What is interesting is what is on
'origin/master' that is still missing from 'master'. For this I think
you have:
$ git log master..origin
-- Sergei.
next prev parent reply other threads:[~2008-03-03 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 12:40 git fetch: where are the downloaded objects stored? Paolo Ciarrocchi
2008-03-03 13:14 ` Matthieu Moy
2008-03-03 14:33 ` Paolo Ciarrocchi
2008-03-03 15:21 ` Matthieu Moy
2008-03-03 15:40 ` Paolo Ciarrocchi
2008-03-03 16:29 ` Nicolas Pitre
2008-03-03 16:51 ` Paolo Ciarrocchi
2008-03-03 17:18 ` Sergei Organov [this message]
2008-03-03 18:14 ` Nicolas Pitre
2008-03-03 18:07 ` Nicolas Pitre
2008-03-03 19:43 ` Paolo Ciarrocchi
2008-03-03 16:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hcfnu3nu.fsf@osv.gnss.ru \
--to=osv@javad.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=paolo.ciarrocchi@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.