It is quite rare to see someone doing such operations on the bare
repository. Instead, you should do the fetch+merge (aka pull) or
fetch+rebase on your local repo (non-bare), and push it back to the bare
Some personal note: I have tons of repositories on my home machine, all of
which have a bare counterpart on a network drive. I don't remember touching
the bare repos directly in the last few years. It is simply unnecessary.
On 27 Jul 2015 07:52, "dexter ietf" <dexter.i...@gmail.com> wrote:
> On Friday, July 24, 2015 at 5:08:00 PM UTC+5:30, Gergely Polonkai wrote:
>> git pull is actually the same as if you write git fetch and then git
>> git-fetch doesn't update anything in your working directory, it just
>> download the changes from the remote. Think about it as if I ask you "what
>> did you change in the code?" You tell me, but I don't apply it to my
>> version yet; that's what git-merge is for.
>> Hi Gergely,
> Thanks for the reply.
> but i don't quiet get it, since its a bare repo i'm not worried about
> merging the tree.
> the remote and bare-repo have diverged, i want to get that latest data
> from the
> remote (latest commits, tags etc..). if this doesn't happen, my bare-repo
> will always
> be out-of-date,maybe i'm using the wrong command. git fetch doesn't seem
> to be
> the right command for the job. i hope i'm clear now.
> thanks again..
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.