From: Chris Packham <judge.packham@gmail.com>
To: jateeq <jawad_atiq@hotmail.com>
Cc: git@vger.kernel.org
Subject: Re: Identifying the last push to a reposiotry
Date: Tue, 2 Mar 2010 13:13:09 -0800 [thread overview]
Message-ID: <a038bef51003021313j40eb5df3ufd9c6e88d8c2b7c@mail.gmail.com> (raw)
In-Reply-To: <27761186.post@talk.nabble.com>
On Tue, Mar 2, 2010 at 1:07 PM, jateeq <jawad_atiq@hotmail.com> wrote:
>
> Hello,
>
> I am trying to list all the modifications to the clone of a repository since
> the clone was last pushed to its original. Is there a way to identify the
> commit id of the HEAD(of the clone) when this last push was carried out?
>
> Thanks,
> Jawad
> --
Something like
git log origin/master..HEAD
Getting more fancy you can do a 'git fetch' first and then you are
able to see what has been pushed to the remote but not pulled locally
as well.
prev parent reply other threads:[~2010-03-02 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 21:07 Identifying the last push to a reposiotry jateeq
2010-03-02 21:13 ` Chris Packham [this message]
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=a038bef51003021313j40eb5df3ufd9c6e88d8c2b7c@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=jawad_atiq@hotmail.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 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).