Re: [GSoC] Proposal: turn git-add--interactive.perl into a builtin

On Sun, Apr 2, 2017 at 4:43 PM, Johannes Schindelin wrote: > We ask to accomplish a microproject before evaluating the proposals for > one reason: to have a good understanding how well the students would > interact with the project if they were accepted. As such, the >

Re: [GSoC] Proposal: turn git-add--interactive.perl into a builtin

Hi Daniel, On Fri, 31 Mar 2017, Daniel Ferreira (theiostream) wrote: > Question: do you suggest any pending bugfix to git-add--interactive or > to something related that might give some useful knowledge in advance? > (for the pre-code period). My microproject involves playing with the >

[RFC] [GSoC] Proposal Draft for GSoC 2017 : Incremental Rewrite of git-submodules

implemented. I also checked out its implementation for linux kernel project , but it seems quite difficult to cover this in my GSoC proposal. Instead, I would run ‘make coverage’ after I port all functions to C. This will also help me find the code for which the test suites aren’t created

Re: [GSoC] Proposal: turn git-add--interactive.perl into a builtin

Well, Google requires me to have a draft on a Google Doc anyway for the proposal, and I am unsure who exactly it will reach. Since it *is* part of the discussion regarding my proposal, I suppose it is worth posting here for anyone to comment:

Re: [GSoC] Proposal: turn git-add--interactive.perl into a builtin

Hi Stefan & Johannes, Thank you for the precious feedback on the proposal. I don't see much sense in sending a full "v2" of it and have you read it all over again, so I'll just answer to your comments directly. Also, although the GSoC website allows me to send a "proposal draft" to you through

Re: [GSoC] Proposal: turn git-add--interactive.perl into a builtin

Hi Stefan & Daniel, On Tue, 28 Mar 2017, Stefan Beller wrote: > On Sat, Mar 25, 2017 at 8:15 PM, Daniel Ferreira (theiostream) > wrote: > > > SYNOPSIS > > There are many advantages to converting parts of git that are still > > scripts to C builtins, among which execution

Re: [GSoC] Proposal: turn git-add--interactive.perl into a builtin

On Sat, Mar 25, 2017 at 8:15 PM, Daniel Ferreira (theiostream) wrote: > SYNOPSIS > There are many advantages to converting parts of git that are still > scripts to C builtins, among which execution speed, improved > compatibility and code deduplication. agreed. >

Re: [GSoC] Proposal Discussion

On Tue, Mar 28, 2017 at 07:52:42AM +0200, Christian Couder wrote: > Hi, > > On Tue, Mar 28, 2017 at 12:17 AM, Devin Lehmacher wrote: > > Hello everyone, > > > > I am a student studying Computer Science at Cornell University. I > > already completed a microproject, Move

Re: [GSoC] Proposal Discussion

Hi, On Tue, Mar 28, 2017 at 12:17 AM, Devin Lehmacher wrote: > Hello everyone, > > I am a student studying Computer Science at Cornell University. I > already completed a microproject, Move ~/.git-credential-cache/socket to > $XDG_CACHE_HOME/credential/socket a week and a

[GSoC] Proposal Discussion

Hello everyone, I am a student studying Computer Science at Cornell University. I already completed a microproject, Move ~/.git-credential-cache/socket to $XDG_CACHE_HOME/credential/socket a week and a half ago or so. I am interested in 2 different projects and would like some advice on them, to

[GSoC] Proposal: turn git-add--interactive.perl into a builtin

Hi there. First of all, I'd like to thank all of the support up to now with my microproject :). Here's a first draft of my proposal for Google Summer of Code '17, based on the "Convert scripts to builtins" idea. Please let me know what you think. --- SYNOPSIS There are many advantages to

Re: [GSoC] Proposal

I had updated the proposal before deadline, if someone is interesting. 2016-03-25 15:12 GMT+08:00 惠轶群 : > Well, I should have done some search before ask. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org

Re: [GSoC] Proposal

Well, I should have done some search before ask. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [GSoC] Proposal

Some developers are already working on that[1]. [1]: http://thread.gmane.org/gmane.comp.version-control.git/288306 On Fri, Mar 25, 2016 at 10:12 AM, 惠轶群 wrote: > There is an interesting idea as an idea for GSoC of 2008, is it still > proposable? > >

Re: [GSoC] Proposal

There is an interesting idea as an idea for GSoC of 2008, is it still proposable? https://git.wiki.kernel.org/index.php/SoC2008Ideas#Restartable_Clone 2016-03-25 11:45 GMT+08:00 惠轶群 : > Hi, > > I'm proposing to take part in GSoC as a developer of git. > > Here is my >

[GSoC] Proposal

Hi, I'm proposing to take part in GSoC as a developer of git. Here is my [Draft](https://docs.google.com/document/d/1zqOVb_cnYcaix48ep1KNPeLpRHvNKA26kNXc78yjhMg/edit?usp=sharing). I'm planning to refactor some part of git. Following is what I'm interested in: - port parts of “git rebase” to a

[GSoC] Proposal

Greetings, I hope it is not yet too late to jump on the Summer of Code bandwagon. I would appreciate comments on my application [1] and my microproject contribution, which will follow this mail as a reply. My proposal mostly stems from what was noted under "convert scripts to builtins" and "git

GSoC proposal

As I was strongly encouraged to submit my GSoC proposal, I'll post it here and CC to my possible mentor. Please, provide with your feedback about my draft. You can also comment it right in the Google doc. Thanks in advance Proposal: https://docs.google.com/document/d

Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

Updated examples with better description for force push and reset HEAD, as suggested by Lars [11]. Thanks and regards, Sidhant Sharma [11]: http://thread.gmane.org/gmane.comp.version-control.git/289365/focus=289495 --- Implement a beginner mode for Git. Abstract Git is a very powerful

Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

On Tuesday 22 March 2016 02:08 PM, Lars Schneider wrote: > On 21 Mar 2016, at 11:19, Sidhant Sharma wrote: > >> Hi, >> I updated the draft with links, ggit usage examples and some changes to the >> timeline. I placed the links with reference here, but in the Google Doc,

Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

On 21 Mar 2016, at 11:19, Sidhant Sharma wrote: > Hi, > I updated the draft with links, ggit usage examples and some changes to the > timeline. I placed the links with reference here, but in the Google Doc, > they're > inline. > > Thanks and regards, > Sidhant Sharma >

Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

Hi, I updated the draft with links, ggit usage examples and some changes to the timeline. I placed the links with reference here, but in the Google Doc, they're inline. Thanks and regards, Sidhant Sharma --- Implement a beginner mode for Git. Abstract Git is a very powerful version control

Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

On Monday 21 March 2016 01:59 PM, Matthieu Moy wrote: > Sidhant Sharma writes: > >> On Monday 21 March 2016 12:22 AM, Matthieu Moy wrote: >> >>> Note that it implies writting an almost full-blown option parser to >>> recognize commands like >>> >>> ggit --work-tree git

Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

Sidhant Sharma writes: > On Monday 21 March 2016 12:22 AM, Matthieu Moy wrote: > >> Note that it implies writting an almost full-blown option parser to >> recognize commands like >> >> ggit --work-tree git --namespace reset --git-dir --hard git log >> >> (just looking for

Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

On Monday 21 March 2016 12:22 AM, Matthieu Moy wrote: > Sidhant Sharma writes: > >> A wrapper is to be implemented around (currently called 'ggit'), which will >> provide the following user interface: >> `ggit ` > There's actually already a tool doing this: > >

Re: [GSOC/RFC] GSoC Proposal Draft | Git Beginner

Sidhant Sharma writes: > Implement a beginner mode for Git. > > Abstract > > Git is a very powerful version control system, with an array of features > that lend the user with great capabilities. But it often so happens that some > beginners are overwhelmed by its

[GSOC/RFC] GSoC Proposal Draft | Git Beginner

Hi, I have drafted my proposal for the project 'Git Beginner', and would like to request your suggestions on improving it. I'm also reading up the Git documentation and the Git ProBook (again) to make notes for the beginner documentation. Would be great to hear your comments on it. Thanks and

Re: [RFC/GSoC] Proposal Draft: Unifying git branch -l, git tag -l, and git for-each-ref

On 03/26/2015 10:07 PM, Jeff King wrote: On Mon, Mar 23, 2015 at 06:39:20PM +0530, karthik nayak wrote: All three commands select a subset of the repository’s refs and print the result. There has been an attempt to unify these commands by Jeff King[3]. I plan on continuing his work[4] and

Re: [RFC/GSoC] Proposal Draft: Unifying git branch -l, git tag -l, and git for-each-ref

On Mon, Mar 23, 2015 at 06:39:20PM +0530, karthik nayak wrote: All three commands select a subset of the repository’s refs and print the result. There has been an attempt to unify these commands by Jeff King[3]. I plan on continuing his work[4] and using his approach to tackle this project.

Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins

Paul Tan pyoka...@gmail.com writes: I think it's still good to have the ideal in mind though (and whoops I forgot to put in the word ideal in the text). Using or not using fork is merely one of the trade-offs we can make. If all other things are equal, no fork is better than a fork is a

Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins

On 24.03.2015 17:37, Paul Tan wrote: I'm applying for git in the Google Summer of Code this year. For my project, I propose to rewrite git-pull.sh and git-am.sh into fast optimized C builtins. I've already hacked up a prototype of a builtin git-pull in [1], and it showed a promising 8x

Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins

On Thu, Mar 26, 2015 at 1:54 AM, Junio C Hamano gits...@pobox.com wrote: Paul Tan pyoka...@gmail.com writes: I think it's still good to have the ideal in mind though (and whoops I forgot to put in the word ideal in the text). Using or not using fork is merely one of the trade-offs we can

Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins

Hi, On Wed, Mar 25, 2015 at 2:37 AM, Junio C Hamano gits...@pobox.com wrote: Paul Tan pyoka...@gmail.com writes: ..., I propose the following requirements for the rewritten code: 1. No spawning of external git processes. This is to support systems with high ``fork()`` or process

[RFC/GSoC] Proposal: Make git-pull and git-am builtins

Hi all, I'm applying for git in the Google Summer of Code this year. For my project, I propose to rewrite git-pull.sh and git-am.sh into fast optimized C builtins. I've already hacked up a prototype of a builtin git-pull in [1], and it showed a promising 8x improvement in execution time on

Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins

On Tue, Mar 24, 2015 at 6:19 PM, Matthieu Moy matthieu@grenoble-inp.fr wrote: A few minor details: on operating systems with poor file system performance (i.e. Windows) = that's not only windows, I also commonly use a slow filesystem on Linux, just because it's NFS. Mentionning other

Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins

Paul Tan pyoka...@gmail.com writes: ..., I propose the following requirements for the rewritten code: 1. No spawning of external git processes. This is to support systems with high ``fork()`` or process creation overhead, and to reduce redundant IO by taking advantage of the internal

Re: [RFC/GSoC] Proposal: Make git-pull and git-am builtins

Paul Tan pyoka...@gmail.com writes: On Tue, Mar 24, 2015 at 6:19 PM, Matthieu Moy matthieu@grenoble-inp.fr wrote: About the timeline: I'd avoid too much parallelism. Usually, it's best to try to send a first patch to the mailing list as soon as possible, hence focus on one point first

[RFC/GSoC] Proposal Draft: Unifying git branch -l, git tag -l, and git for-each-ref

missed out on, in the proposal. GSOC Proposal : Unifying git branch -l, git tag -l, and git for-each-ref # Main objectives of the project: * Build a common

Fwd: [RFC] [GSoC Proposal Draft] Unifying git branch -l,git tag -l and git for-each-ref

Hi all, I have attempted a microproject [1][2] and this is my first draft of the proposal.I have included only the matter regarding my approach to solving the problem and shall add my personal details later. Please be kind enough to go through my proposal and suggest modifications or detailing

Re: [RFC][GSOC] Proposal Draft for GSoC, Suggest Changes

Hello, Now that i have already submitted my proposal to GSOC , i was wondering if there is any way where i could contribute to git via bug fixes or something similar to the microprojects which was available prior to GSOC application. Also wondering if any clarification was needed as per my

Re: GSoC proposal: port pack bitmap support to libgit2.

Hi, Sorry for this late reply, I was busy for past few days. On Fri, Mar 14, 2014 at 12:34 PM, Jeff King p...@peff.net wrote: On Wed, Mar 12, 2014 at 04:19:23PM +0800, Yuxuan Shui wrote: I'm Yuxuan Shui, a undergraduate student from China. I'm applying for GSoC 2014, and here is my proposal:

[RFC][GSOC] Proposal Draft for GSoC, Suggest Changes

basis and would be able to contribute to the project even after GSOC. Proposal Ideas Page : Git configuration API improvements The Following improvements have to be made to how configs are handled in git : Read all the config files once and store them in an appropriate data structure. I suggest

Re: GSoC proposal: port pack bitmap support to libgit2.

Hi, On Wed, Mar 12, 2014 at 4:19 PM, Yuxuan Shui yshu...@gmail.com wrote: Hi, I'm Yuxuan Shui, a undergraduate student from China. I'm applying for GSoC 2014, and here is my proposal: I found this idea on the ideas page, and did some research about it. The pack bitmap patchset add a new

Re: GSoC proposal: port pack bitmap support to libgit2.

On Wed, Mar 12, 2014 at 04:19:23PM +0800, Yuxuan Shui wrote: I'm Yuxuan Shui, a undergraduate student from China. I'm applying for GSoC 2014, and here is my proposal: I found this idea on the ideas page, and did some research about it. The pack bitmap patchset add a new .bitmap file for

GSoC proposal: port pack bitmap support to libgit2.

Hi, I'm Yuxuan Shui, a undergraduate student from China. I'm applying for GSoC 2014, and here is my proposal: I found this idea on the ideas page, and did some research about it. The pack bitmap patchset add a new .bitmap file for every pack file which contains the reachability information of