From: Junio C Hamano <junkio@cox.net>
To: "Aneesh Kumar" <aneesh.kumar@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git pull origin doesn't update the master
Date: Mon, 10 Apr 2006 00:24:42 -0700 [thread overview]
Message-ID: <7vmzetao5h.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <cc723f590604092345r7d0e2cedr8f9838d054ecb023@mail.gmail.com> (Aneesh Kumar's message of "Mon, 10 Apr 2006 12:15:36 +0530")
"Aneesh Kumar" <aneesh.kumar@gmail.com> writes:
> Work flow is now a bit complicated. I clone the repository. Now i need
> to edit remotes/origin to make sure what all branches i need to
> follow. And then do a git pull origin. Earlier i just need to do a
> clone and a git pull. I don't need to fast forward pu branch.
What you are saying is that the previous round did a wrong thing
without telling the user, and it just happened that you did not
care about the wrong thing it did.
It is a gentle reminder that heads that are rewound need to be
advertised as such. It is conceivable that in future versions
of git we might want to be able to mark some branches "this is
expected to be rewound" explicitly and make the clone operation
to take notice, to give you the plus sign automatically.
prev parent reply other threads:[~2006-04-10 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 4:41 git pull origin doesn't update the master Aneesh Kumar
2006-04-10 4:51 ` Aneesh Kumar
[not found] ` <20060410010316.2aec94ae.seanlkml@sympatico.ca>
2006-04-10 5:03 ` sean
2006-04-10 6:29 ` Junio C Hamano
2006-04-10 6:45 ` Aneesh Kumar
2006-04-10 7:24 ` Junio C Hamano [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=7vmzetao5h.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=aneesh.kumar@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