From: Sverre Rabbelier <srabbelier@gmail.com>
To: Harry Johnson <hjohnson@viasic.com>
Cc: git@vger.kernel.org
Subject: Re: Noob question regarding git push
Date: Wed, 19 Jan 2011 23:50:27 +0100 [thread overview]
Message-ID: <AANLkTik5QOoWNjUP8LvRE=AmiAtmchc8NND9aKDe2svR@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=X8PURGSX5ODHpXACUWuA0oioTkeNEmRVnkx1D@mail.gmail.com>
Heya,
On Wed, Jan 19, 2011 at 23:30, Harry Johnson <hjohnson@viasic.com> wrote:
> What's the proper technique for making sure you see the actual changes
> that were pushed to a repo?
I think this is the FAQ you want:
https://git.wiki.kernel.org/index.php/GitFaq#Why_won.27t_I_see_changes_in_the_remote_repo_after_.22git_push.22.3F
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2011-01-19 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 22:30 Noob question regarding git push Harry Johnson
2011-01-19 22:50 ` Sverre Rabbelier [this message]
2011-01-19 23:10 ` Harry Johnson
2011-01-20 2:35 ` Alex Budovski
2011-01-19 22:56 ` Junio C Hamano
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='AANLkTik5QOoWNjUP8LvRE=AmiAtmchc8NND9aKDe2svR@mail.gmail.com' \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=hjohnson@viasic.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).