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

Re: Git GSoC 2014

From
Jeff King <peff@peff.net>
Date
Feb 14, 2014, 10:41 UTC
Message-ID
<20140214104139.GA28570@sigill.intra.peff.net>
In-Reply-To
<CALkWK0mR=9ZD256bHx9d=W9ayqn5bOETWBQLW_kvRSy-GeQK4Q@mail.gmail.com>
On Thu, Feb 13, 2014 at 06:17:17PM -0500, Ramkumar Ramachandra wrote:
> I'll throw in a few ideas from half-finished work.
Thanks. A few comments:
Show 8 quoted lines
> 1. Speed up git-rebase--am.sh
> 
> Currently, git-rebase--am.sh is really slow because it dumps each
> patch to a file using git-format-patch, and picks it up to apply
> subsequently using git-am. Find a way to speed this up, without
> sacrificing safety. You can use the continuation features of
> cherry-pick, and dump to file only to persist state in the case of a
> failure.
Isn't the merge backend faster? I thought that was the point of it.
Show 7 quoted lines
> 3. Rewrite git-branch to use git-for-each-ref
> 
> For higher flexibility in command-line options and output format, use
> git for-each-ref to re-implement git-branch. The first task is to grow
> features that are in branch but not fer into fer (like --column,
> --merged, --contains). The second task is to refactor fer so that an
> external program can call into it.

I actually have this about 95% done, waiting for the patches to be polished. So I don't think it makes a good GSoC project (it would be stupid to start from scratch, and polishing my patches is a lame project).

Show 7 quoted lines
> 4. Implement @{publish}
> (I just can't find the time to finish this)
> 
> @{publish} is a feature like @{upstream}, showing the state of the
> publish-point in the case of triangular workflows. Implement this
> while sharing code with git-push, and polish it until the prompt shows
> publish-state.

I think this could be a good GSoC-sized topic. I'm going to adjust the title to be "better support for triangular workflows". I think they may want to examine other issues in the area, rather than drilling down on @{publish} in particular (but ultimately, it is up to the student to propose what they want to do).

-Peff
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 12 of 15 in “Git GSoC 2014”
  1. Jeff KingFeb 13, 2014
  2. Thomas RastFeb 13, 2014
  3. Junio C HamanoFeb 13, 2014
  4. Thomas RastFeb 14, 2014
  5. David KastrupFeb 14, 2014
  6. Thomas RastFeb 15, 2014
  7. Duy NguyenFeb 15, 2014
  8. David KastrupFeb 15, 2014
  9. Shawn PearceFeb 15, 2014
  10. Vicent MartíFeb 14, 2014
  11. Ramkumar RamachandraFeb 13, 2014
  12. Jeff KingFeb 14, 2014
  13. Ramkumar RamachandraFeb 14, 2014
  14. Jeff KingFeb 14, 2014
  15. Jeff KingFeb 14, 2014

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.