From: ir0s <imirene@gmail.com>
To: git@vger.kernel.org
Subject: Re: Local branch ahead of tracked remote branch but git push claims everything up-to-date
Date: Thu, 21 Aug 2008 08:35:38 -0700 (PDT) [thread overview]
Message-ID: <1219332938839-740444.post@n2.nabble.com> (raw)
In-Reply-To: <7v4p5fnw3i.fsf@gitster.siamese.dyndns.org>
Sorry if you get this twice, oddly my first attempt to send this bounced.
Thank you for all the good advice however, none of it seemed to resolve my
issue.
Attempting to call:
$git push origin mybranch
Results in the same message: Everything up to date =/
I also tried to call $git fetch origin just in case, and doing a pull
doesn't return anything (which makes sense, no one pushed anything to the
branch -- although I seem to be the only one with this issue.)
Could my branch have somehow diverged from the origin remotebranch?
-- Irene
Junio C Hamano wrote:
>
> Daniel Barkalow <barkalow@iabervon.org> writes:
>
>> That is actually to say that fetch should do it (pull calls fetch for
>> that
>> part), and I agree with that, assuming you've actually got that fetch
>> config, of course.
>
> Hmm, traditionally, an explicit refspec on the command line that does not
> store overrides the configured ones that do store, and I've been using it
> as a feature when I run test fetches. If I do not like fetched result, I
> can tell the other guy to fix his history and I do not have to contaminate
> the history my tracking ref points at. IOW, I use my tracking refs not
> just "this is where the guy is", but "this is the last good one I fetched
> from that guy".
>
> I could be persuaded to use reflog (e.g. "git diff his@{1}..his") and
> manual tagging (i.e. "git tag -f last-good-his his") myself, but this is
> "I'd _tolerate_ such a change myself", certainly not "I am happy with that
> change and I'd help you guys advocate it and try convincing others who
> shared my expectations to switch to reglog and manual tagging."
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
View this message in context: http://n2.nabble.com/Local-branch-ahead-of-tracked-remote-branch-but-git-push-claims-everything-up-to-date-tp736663p740444.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-08-21 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 20:26 Local branch ahead of tracked remote branch but git push claims everything up-to-date ir0s
2008-08-20 20:37 ` Alex Riesen
2008-08-20 20:40 ` Andreas Färber
2008-08-20 21:01 ` Avery Pennarun
2008-08-20 21:15 ` Junio C Hamano
2008-08-20 21:22 ` Avery Pennarun
2008-08-20 22:25 ` Daniel Barkalow
2008-08-20 22:46 ` Junio C Hamano
2008-08-21 15:35 ` ir0s [this message]
2008-08-21 16:22 ` Michael J Gruber
2008-08-21 16:53 ` ir0s
2008-08-22 14:09 ` Michael J Gruber
2008-08-21 16:55 ` ir0s
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=1219332938839-740444.post@n2.nabble.com \
--to=imirene@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).