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

Re: 'upstream' branches.

From
Alex Riesen <raa.lkml@gmail.com>
Date
May 7, 2007, 08:39 UTC
Message-ID
<81b0412b0705070139v49f045d2j3929b38846e20120@mail.gmail.com>
In-Reply-To
<7vtzup6pzl.fsf@assigned-by-dhcp.cox.net>
On 5/7/07, Junio C Hamano <junkio@cox.net> wrote:
> >
> > Maybe we should not fail in the case the remote repo is older then
> > local, but just to try to fast-forward local reference after a fetch
> > and fail only if the fast-forward fails?
...
>
> Something like this untested patch should be sufficient if we
> want to go this route, but I am not convinced yet that this is
> the right thing to do.  ...

Now, after I thought about that a bit more (and after your explanation about David being silly), I think I was kind of silly as well.

The idea looks a bit dangerous (because of the local and remote can divert from each other). If any, the reference mapping syntax should clearly reveal that, more like

    "TRY-FAST-FORWARD-MERGE ref1:ref2"

instead of that hideous minus. And come to think about that, I'd still prefer to do that manually, as a real merge (I cannot know in advance _when_ the repos divert, and which one of source repos will divert, to entrust the operation an unattended process, and I have get-fetch in cron files sometimes), so count me out as a user of that feature.

Previous: Junio C Hamano
Message 13 of 13 in “'upstream' branches.”
  1. David WoodhouseMay 5, 2007
  2. Alex RiesenMay 5, 2007
  3. David WoodhouseMay 5, 2007
  4. Alex RiesenMay 5, 2007
  5. Junio C HamanoMay 6, 2007
  6. David WoodhouseMay 6, 2007
  7. Junio C HamanoMay 6, 2007
  8. David WoodhouseMay 6, 2007
  9. Junio C HamanoMay 7, 2007
  10. David WoodhouseMay 7, 2007
  11. Alex RiesenMay 6, 2007
  12. Junio C HamanoMay 7, 2007
  13. Alex RiesenMay 7, 2007

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.