git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to update a cloned git repository

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Sep 11, 2012, 14:09 UTC
Message-ID
<CAMK1S_jXA0WfC-de=mD7-+2oJiep_A2rKSZdSsqn7CcNJPsq5A@mail.gmail.com>
In-Reply-To
<006f01cd900e$fce59a60$f6b0cf20$@schmitz-digital.de>

On Tue, Sep 11, 2012 at 4:47 PM, Joachim Schmitz <jojo@schmitz-digital.de> wrote:

> Like this?
> git pull --rebase HEAD~42
>
> So far I create patches, wiped out the entire repository, cloned, forked and applied the changes, pretty painful.
I think a 'git pull --rebase' should usually work even for 'pu'.

But sometimes pu may have changes that take away the basis for your patch (i.e, not just a restructure) then you'd get conflicts.

Previous: Matthieu MoyNext: Junio C Hamano
Message 5 of 14 in “How to update a cloned git repository”
  1. Joachim SchmitzSep 11, 2012
  2. Matthieu MoySep 11, 2012
  3. Joachim SchmitzSep 11, 2012
  4. Matthieu MoySep 11, 2012
  5. Sitaram ChamartySep 11, 2012
  6. Junio C HamanoSep 11, 2012
  7. Joachim SchmitzSep 11, 2012
  8. Matthieu MoySep 11, 2012
  9. Joachim SchmitzSep 11, 2012
  10. Erik Faye-LundSep 11, 2012
  11. Junio C HamanoSep 11, 2012
  12. Matthieu MoySep 11, 2012
  13. Joachim SchmitzSep 11, 2012
  14. Matthieu MoySep 12, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.