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

Re: [PATCH 0/6] Make pull a builtin

From
Paul Tan <pyokagan@gmail.com>
Date
May 6, 2015, 04:27 UTC
Message-ID
<CACRoPnR0+Ovnnz=HzRA7ZsHHUQ54JrPfih5E8wsRaKY-ajf-gA@mail.gmail.com>
In-Reply-To
<1430870453-5408-1-git-send-email-stephen.robin@gmail.com>
Hi Stephen,
On Wed, May 6, 2015 at 8:00 AM, Stephen Robin <stephen.robin@gmail.com> wrote:
Show 19 quoted lines
> Hi Paul,
>
> Congratulations on getting your project accepted for GSOC. Here's my
> attempt at implementing pull as a builtin, maybe it will be of some use
> as you look to progress your version.
>
> It's fairly complete in the sense that all the features of git-pull.sh
> should be implemented, the test suite passes, and I've been using it
> myself without issue. At the same time it's some way from finished as
> I've never had time to test it fully and there are parts of the code I'm
> not happy with.
>
> Apologies for not sharing this with you earlier.  I have been too busy
> with paid work to look at any open source projects for some months.
>
> Good luck with your project!
>
> Regards
> Stephen
Thank you so much for sharing your work. I'll be referencing this.

Regards, Paul

Previous: Stephen RobinNext: karthik nayak
Message 12 of 13 in “GSoC 2015: 2 accepted proposals”
  1. Matthieu MoyApr 27, 2015
  2. Paul TanApr 28, 2015
  3. Johannes SchindelinApr 29, 2015
  4. 0/6 Make pull a builtinStephen Robin, May 6, 2015
  5. 1/6 merge: tidy up optionsStephen Robin, May 6, 2015
  6. 2/6 merge: move error message given when a merge needs committing to advice.cStephen Robin, May 6, 2015
  7. 3/6 merge-base: split handle_fork_point to make reuse easierStephen Robin, May 6, 2015
  8. 4/6 pull: reimplement as a builtin in CStephen Robin, May 6, 2015
  9. 5/6 pull: allow interactive rebaseStephen Robin, May 6, 2015
  10. Johannes SchindelinMay 6, 2015
  11. 6/6 parse-remote: dismantle git-parse-remote.shStephen Robin, May 6, 2015
  12. Paul TanMay 6, 2015
  13. karthik nayakApr 28, 2015

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.