Re: GSoC 2016 | Proposal | Incremental Rewrite of git bisect

On Fri, Mar 25, 2016 at 5:10 PM, Christian Couder wrote: > On Fri, Mar 25, 2016 at 11:15 AM, Pranit Bauva wrote: >>> - you will add an option to "git bisect--helper" to perform what the >>> git-bisect.sh function did, and >>> - you will create a test script for "git bisect--helper" in which you >

Re: GSoC 2016 | Proposal | Incremental Rewrite of git bisect

On Fri, Mar 25, 2016 at 11:15 AM, Pranit Bauva wrote: >> - you will add an option to "git bisect--helper" to perform what the >> git-bisect.sh function did, and >> - you will create a test script for "git bisect--helper" in which you >> will test each option? > > I had very initially planned to do

Re: GSoC 2016 | Proposal | Incremental Rewrite of git bisect

> - you will add an option to "git bisect--helper" to perform what the > git-bisect.sh function did, and > - you will create a test script for "git bisect--helper" in which you > will test each option? I had very initially planned to do this. But Matthieu pointed out that it would be much better t

Re: GSoC 2016 | Proposal | Incremental Rewrite of git bisect

On Fri, Mar 25, 2016 at 2:45 PM, Matthieu Moy wrote: > Christian Couder writes: > >> On Thu, Mar 24, 2016 at 12:27 AM, Pranit Bauva >> wrote: >> >>> Unification of bisect.c and bisect--helper.c >>> >>> This will unify the algorithmic and non-algorithmic parts of bisect >>> bringing them under o

Re: GSoC 2016 | Proposal | Incremental Rewrite of git bisect

On Fri, Mar 25, 2016 at 2:32 PM, Christian Couder wrote: > On Thu, Mar 24, 2016 at 12:27 AM, Pranit Bauva wrote: >> Hey! >> >> I have prepared a proposal for Google Summer of Code 2016. I know this >> is a bit late, but please try to give your comments and suggestions. >> My proposal could greatl

Re: Regarding GSoC 2016

Mehul Jain wrote: > On Thu, Mar 24, 2016 at 11:13 PM, Saurabh Jain > wrote: > > The proposal can be accessed here. > > > 5mWF_cqoZS6IUvGr6CVu5SmkbZk/edit?usp=sharing> > > It's broken I guess. Not sure what you mean by that, personally I ha

Re: GSoC 2016 | Proposal | Incremental Rewrite of git bisect

Christian Couder writes: > On Thu, Mar 24, 2016 at 12:27 AM, Pranit Bauva wrote: > >> Unification of bisect.c and bisect--helper.c >> >> This will unify the algorithmic and non-algorithmic parts of bisect >> bringing them under one heading to make the code clean. > > I am not sure this is needed

Re: GSoC 2016 | Proposal | Incremental Rewrite of git bisect

On Thu, Mar 24, 2016 at 12:27 AM, Pranit Bauva wrote: > Hey! > > I have prepared a proposal for Google Summer of Code 2016. I know this > is a bit late, but please try to give your comments and suggestions. > My proposal could greatly improve from this. Some questions: > > 1. Should I include more

Re: Regarding GSoC 2016

On Thu, Mar 24, 2016 at 11:13 PM, Saurabh Jain wrote: > The proposal can be accessed here. > 5mWF_cqoZS6IUvGr6CVu5SmkbZk/edit?usp=sharing> It's broken I guess. Also Cc Carlos Martín Nieto . He is one of the possible mentor on this one. >

Regarding GSoC 2016

Hi, I know it's bit too late but I was busy with some other stuff. I have applied for GSoC under libgit for this project "Port packfile creation optimisations to libgit2". I request all the mentors and concerned people to please review my proposal and suggest some possible changes. The proposa

Re: GSoC 2016: application period ongoing, deadline = tomorrow

Hi, The GSoC deadline is approaching. A few reminders for students: * You need to submit a final application before the (strict) deadline. Your draft won't be turned into a final version automatically. * You may submit your "final application" multiple times. We (admins & mentors) don't see

GSoC 2016 | Proposal | Incremental Rewrite of git bisect

Hey! I have prepared a proposal for Google Summer of Code 2016. I know this is a bit late, but please try to give your comments and suggestions. My proposal could greatly improve from this. Some questions: 1. Should I include more ways in which it can help windows? 2. Should I include the functio

Re: GSoC 2016: application period ongoing, a few advices

Hi On 03/19/2016 01:26 PM, Matthieu Moy wrote: > As a reminder, the GSoC students application period has started (since > March 14, deadline = March 25th = soon). Thanks for the reminder. Because you might be expecting a proposal from me, I just wanted to let you know, that I was too busy lately

GSoC 2016: application period ongoing, a few advices

Hi, Recipients of this email: the Git list, mentors and admins (I tried to use the address you normally use, or the one on the GSoC site. Let me know if I shall use another one), and students who showed interest in GSoC (I may have missed some ...). Bcc-ed is a student who applied via the web inte

Re: Git has been accepted as a GSoC 2016 mentor organization!

On Tue, Mar 08, 2016 at 05:46:25PM -0500, Jeff King wrote: > Most of the resources are just pointers to our GSoC stuff. This does > mean I've effectively signed our mentors up to participate in this > program. I hope that's OK, as it's effectively the same commitment as > GSoC (and obviously we w

Re: Git has been accepted as a GSoC 2016 mentor organization!

On Wed, Mar 09, 2016 at 10:55:00AM +0100, Matthieu Moy wrote: > > Most of the resources are just pointers to our GSoC stuff. This does > > mean I've effectively signed our mentors up to participate in this > > program. I hope that's OK, > > Not sure whether I was supposed to receive something, b

Re: Git has been accepted as a GSoC 2016 mentor organization!

Hi Peff, On Tue, 8 Mar 2016, Jeff King wrote: > I've effectively signed our mentors up to participate in this program. > I hope that's OK Speaking for myself, I think this is more than just okay. I really like the idea of more diversity in the Git community. Ciao, Dscho -- To unsubscribe from t

Re: Git has been accepted as a GSoC 2016 mentor organization!

Jeff King writes: > I've also signed us up for Outreachy, which is an internship program > designed to encourage open source participation by under-represented > groups. Good. In the case of the Git community, "under-represented" may even be a euphemism as it is now :-\. > Most of the resources

Re: Git has been accepted as a GSoC 2016 mentor organization!

On Tue, Mar 08, 2016 at 03:01:47PM -0800, Junio C Hamano wrote: > Jeff King writes: > > > I've also signed us up for Outreachy, which is an internship program > > designed to encourage open source participation by under-represented > > groups. Details are here: > > > > https://www.gnome.org/ou

Re: Git has been accepted as a GSoC 2016 mentor organization!

Jeff King writes: > I've also signed us up for Outreachy, which is an internship program > designed to encourage open source participation by under-represented > groups. Details are here: > > https://www.gnome.org/outreachy/ > > but I'll try to summarize here what it means for us. https://wiki

Re: Git has been accepted as a GSoC 2016 mentor organization!

On Mon, Feb 29, 2016 at 10:01:52PM +0100, Matthieu Moy wrote: > Hi, > > This is my pleasure to inform you all that Git has just been accepted as > a GSoC mentor organization. > > https://summerofcode.withgoogle.com/organizations/?sp-page=3 > > I've invited Johannes, Stefan, Christian and Lars

Re: GSoC 2016 Microproject

On 03/01, Sidhant Sharma wrote: > > > If you use PARSE_OPT_HIDDEN, I think you don't need to specify a message. > > Otherwise, the documentation only has value if it contains more than just > > the option name, but that is the hard part if you're not familiar with the > > code. The best place to

Re: GSoC 2016 Microproject

> If you use PARSE_OPT_HIDDEN, I think you don't need to specify a message. > Otherwise, the documentation only has value if it contains more than just the > option name, but that is the hard part if you're not familiar with the code. > The best place to find documentation is in the history (gi

Git has been accepted as a GSoC 2016 mentor organization!

Hi, This is my pleasure to inform you all that Git has just been accepted as a GSoC mentor organization. https://summerofcode.withgoogle.com/organizations/?sp-page=3 I've invited Johannes, Stefan, Christian and Lars as potential mentors for Git, and Carlos to represent libgit2. I also took the

Re: GSoC 2016 Microproject

Sidhant Sharma writes: >>> First, I'm not quite sure what to put in the help message for the >>> options (--quiet, --stateless-rpc, --advertise-refs and >>> --reject-thin-pack-for-testing). >> They are currently undocumented. We sometimes have explicitly >> undocumented options (PARSE_OPT_HIDDEN)

Re: GSoC 2016 Microproject

>> First, I'm not quite sure what to put in the help message for the >> options (--quiet, --stateless-rpc, --advertise-refs and >> --reject-thin-pack-for-testing). > They are currently undocumented. We sometimes have explicitly > undocumented options (PARSE_OPT_HIDDEN) when they are used only > in

Re: GSoC 2016 Microproject

Sidhant Sharma writes: > Hi, >> I didn't see anything going on for this one, but you may want to >> double-check with the ml's archives. >> > I checked the archives and there doesn't seem to be any active work on this. > I made the required changes and ran the test suite. Though all the > tests p

Re: GSoC 2016 Microproject

Hi, Should I make a patch for this and submit it for discussion on the mailing list? Regards, Sidhant Sharma [:tk] -- 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.

Re: GSoC 2016 Microproject

Hi, > I didn't see anything going on for this one, but you may want to > double-check with the ml's archives. > I checked the archives and there doesn't seem to be any active work on this. I made the required changes and ran the test suite. Though all the tests pass, there still are two queries I

Re: GSoC 2016 Microproject

Sidhant Sharma writes: >> There's already work in progress on this project, see the mailing list >> the last few days. >> > > Okay, in that case, I'd like to try is the one titled "Make upload-pack > and receive-pack use the parse-options api". In that, I can take up > the `builtin/receive-pack.c

Re: GSoC 2016 Microproject

> There's already work in progress on this project, see the mailing list > the last few days. > Okay, in that case, I'd like to try is the one titled "Make upload-pack and receive-pack use the parse-options api". In that, I can take up the `builtin/receive-pack.c` file. Would that be okay? Than

Re: GSoC 2016 Microproject

Sidhant Sharma writes: > Hi everyone, > > > I'm Sidhant Sharma. I'm looking to participate in GSoC 2016 (and contribute > to Git in general as well). I read up the pages relating to participation > in GSoC and selected the microproject "Add configuration o

GSoC 2016 Microproject

Hi everyone, I'm Sidhant Sharma. I'm looking to participate in GSoC 2016 (and contribute to Git in general as well). I read up the pages relating to participation in GSoC and selected the microproject "Add configuration options for some commonly used command-line option

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Tue, Feb 23, 2016 at 02:13:34PM +0100, Matthieu Moy wrote: > > So I think a little back and forth is good; almost everybody does > > something a little wrong in their first patch submission. But I'd worry > > about a topic that is going to involve a lot of bikeshedding or subtle > > nuances to

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Jeff King writes: > On Mon, Feb 22, 2016 at 01:56:52PM -0800, Junio C Hamano wrote: > >> Jeff King writes: >> >> > I agree that there are a lot of different ways to resolve each instance, >> > and it will vary from case to case. I think the original point of a >> > microproject was to do someth

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Mon, Feb 22, 2016 at 01:56:52PM -0800, Junio C Hamano wrote: > Jeff King writes: > > > I agree that there are a lot of different ways to resolve each instance, > > and it will vary from case to case. I think the original point of a > > microproject was to do something really easy and not cont

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Jeff King writes: > I agree that there are a lot of different ways to resolve each instance, > and it will vary from case to case. I think the original point of a > microproject was to do something really easy and not contentious, so > that the student could get familiar with all of the other par

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Mon, Feb 22, 2016 at 11:22:48AM +0100, Matthieu Moy wrote: > > Idea for microprojects. If you compile using gcc with -Wshadow, it > > spots local variables that shadow another local or global variables. > > These are usually bad because it makes it's easy to make mistakes when > > changing the

Re: GSoC 2016: Microproject

On Mon, Feb 22, 2016 at 4:51 PM, Duy Nguyen wrote: > OK server is up but very likely misconfigured. If you have experience > with http server before (I think this is apache), then you can dig in > t/lib-httpd.sh, study how the server is configured and try to fix it. Thanks Duy. :) All tests pass

Re: GSoC 2016: Microproject

On Mon, Feb 22, 2016 at 5:30 PM, Mehul Jain wrote: > On Mon, Feb 22, 2016 at 3:50 PM, Duy Nguyen wrote: >> You may have an http server installed but not suitable for these >> tests. Try running one test file alone with -v -i, e.g. >> ./t5539-fetch-http-shallow.sh -v -i and post the output. > > He

Re: GSoC 2016: Microproject

> On 22 Feb 2016, at 11:21, Lars Schneider wrote: > > >> On 22 Feb 2016, at 11:12, Mehul Jain wrote: >> >> On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy >> wrote: >>> The simplest way to get back on track for you is probably to start over >>> with a fresh clone, or (warning: destructive ope

Re: GSoC 2016: Microproject

> On 22 Feb 2016, at 11:12, Mehul Jain wrote: > > On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy > wrote: >> The simplest way to get back on track for you is probably to start over >> with a fresh clone, or (warning: destructive operations): use git clean >> to remove untracked files. > > Hell

Re: GSoC 2016: Microproject

On Mon, Feb 22, 2016 at 3:50 PM, Duy Nguyen wrote: > You may have an http server installed but not suitable for these > tests. Try running one test file alone with -v -i, e.g. > ./t5539-fetch-http-shallow.sh -v -i and post the output. Here's the output :- expecting success: git clone --bare

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Duy Nguyen writes: > On Sat, Feb 13, 2016 at 6:21 PM, Matthieu Moy > wrote: >> Less urgent, but we need to add more stuff to be credible: >> >> ... >> >> http://git.github.io/SoC-2016-Microprojects/ => I just did s/2015/2016/. >> I think most projects are not valid anymore, and we need new ones.

Re: GSoC 2016: Microproject

On Mon, Feb 22, 2016 at 5:12 PM, Mehul Jain wrote: > On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy > wrote: >> The simplest way to get back on track for you is probably to start over >> with a fresh clone, or (warning: destructive operations): use git clean >> to remove untracked files. > > Hell

Re: GSoC 2016: Microproject

On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy wrote: > The simplest way to get back on track for you is probably to start over > with a fresh clone, or (warning: destructive operations): use git clean > to remove untracked files. Hello Matthieu, I followed your advise and cloned a fresh copy of

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Sat, Feb 13, 2016 at 6:21 PM, Matthieu Moy wrote: > Less urgent, but we need to add more stuff to be credible: > > ... > > http://git.github.io/SoC-2016-Microprojects/ => I just did s/2015/2016/. > I think most projects are not valid anymore, and we need new ones. > > To all: please contribute

Re: GSoC 2016: Microproject

Please, don't top-post on this list. Mehul Jain writes: > Hello, > > I faced the following problem when I tested master branch. Here I have > made no commits to master branch. Are you sure that 1) you have no uncommitted change and 2) you have compiled what you have in your tree? > Is this tes

Re: GSoC 2016: Microproject

On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy wrote: > Mehul Jain writes: > >> Earlier when I was testing the master branch on my pc, I used "make" >> in \t directory, which lead to failure of test #2, #3 in >> t5539-fetch-http-shallow.sh . >> Afterwards I switched to sudo mode and ran the make

Re: GSoC 2016: Microproject

Mehul Jain writes: > Earlier when I was testing the master branch on my pc, I used "make" > in \t directory, which lead to failure of test #2, #3 in > t5539-fetch-http-shallow.sh . > Afterwards I switched to sudo mode and ran the make command again. Never ever do that. Your git source tree shoul

Re: GSoC 2016: Microproject

On Sun, Feb 21, 2016 at 10:25 AM, Matthieu Moy wrote: > Please, don't top-post on this list. I apologize for top-posting on the list. > Are you sure that 1) you have no uncommitted change and 2) you have > compiled what you have in your tree? 1) Yes, I have no uncommited change in the branch(ma

Re: GSoC 2016: Microproject

On Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller wrote: > Yes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right > place as judging from the file name of the tests. I checked out both of the files and made following observations - 1) As I'm going to add an option for "git

Re: GSoC 2016: Microproject

]: *** [t5539-fetch-http-shallow.sh] Error 1 make[1]: Leaving directory `/home/mj/git/t' make: *** [test] Error 2 Is this test failure usual with linux based system or just happened with me. I'm running Ubuntu 14.04. thanks, Mehul Jain On Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller wrot

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Hi Junio, On Fri, 19 Feb 2016, Junio C Hamano wrote: > The "experimenting" would include mergy operations like "am -3" and > "cherry-pick". "After queuing a topic and trying it in isolation, an > attempt to merge to the baseline results in quite a mess, and I give > up"--there is nothing to salv

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Lars Schneider writes: > If this mode is enabled then Git shall print a warning message before > running a potentially destructive command. In addition to the warning > Git shall print a command that would reverse the operation if possible. > Most of the information to reverse an operation is

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Matthieu Moy writes: >> We have these "powerful" tools for a reason. After making a mess >> experimenting with your working tree files, "reset --hard" is the >> best tool to go back to the known-good state, > > I disagree with that. This reminds me a discussion I had with a student > a few years

Re: GSoC 2016: Microproject

On Fri, Feb 19, 2016 at 11:20 PM, Stefan Beller wrote: > Yes, most likely t/t5521-pull-options.sh or t/t5520-pull.sh would be the right > place as judging from the file name of the tests. Thanks for specifying the files. I think t/t5520-pull.sh line 258 will be the best place to write test for th

Re: GSoC 2016: Microproject

On Fri, Feb 19, 2016 at 9:39 AM, Mehul Jain wrote: > On Fri, Feb 19, 2016 at 6:33 PM, Matthieu Moy > wrote: >> Hi, >> >> This is a double-post. You've posted almost the same message under the >> title "GSoC 2016". Nothing serious, but attention to

Re: GSoC 2016: Microproject

On Fri, Feb 19, 2016 at 6:33 PM, Matthieu Moy wrote: > Hi, > > This is a double-post. You've posted almost the same message under the > title "GSoC 2016". Nothing serious, but attention to details is > important if you want to give a good image of yourself. I'm

Re: GSoC 2016: Microproject

Hi, This is a double-post. You've posted almost the same message under the title "GSoC 2016". Nothing serious, but attention to details is important if you want to give a good image of yourself. Mehul Jain writes: > Hello everyone, > > I'm Mehul Jain. I'm look

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Lars Schneider writes: > Thanks for your elaborate response. I think I got your point and I > tried to adjust my "beginner mode" proposal accordingly [1]. Now merged as https://github.com/git/git.github.io/commit/6b8b5e19cdb221192dedd70ba3e207636f1cdab1 I've added a warning for students: Not

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On 02/18, Lars Schneider wrote: > > On 17 Feb 2016, at 19:58, Matthieu Moy wrote: > > > Lars Schneider writes: > > > >> Coincidentally I started working on similar thing already (1) and I have > >> lots of ideas around it. > > > > I guess it's time to start sharing these ideas then ;-). > > > > I

Re: GSoC 2016: applications open, deadline = now => submitted

On Fri, Feb 19, 2016 at 10:10:55AM +0100, Matthieu Moy wrote: > > I think we can continue to modify up to the deadline (at least that has > > been the case in years past). > > Indeed: I've completed the application and it's still possible to modify > (the form just says "You've completed this for

Re: GSoC 2016: applications open, libgit2 and git.git

On Fri, 2016-02-19 at 09:06 +0100, Matthieu Moy wrote: > Carlos Martín Nieto writes: > > > We still have most of the same things open as for the 2014 list. > > I'll > > ask around to see if we have. Last year I wasn't involved in the > > candidate selection but IIRC we didn't do a project as none

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Fri, Feb 19, 2016 at 2:17 PM, Matthieu Moy wrote: >> with David's multiple ref backend work, we could have a third, >> no-dependency backend. We can use index format to store refs. > > This sounds like an interesting but ambitious project for a GSoC. There > are a lot of new stuff to understand

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On 18 Feb 2016, at 20:13, Junio C Hamano wrote: > Stefan Beller writes: > >> On Thu, Feb 18, 2016 at 12:41 AM, Lars Schneider >> wrote: Feel free to start writting an idea for http://git.github.io/SoC-2016-Ideas/. It'd be nice to have a few more ideas before Friday. We can poli

Re: GSoC 2016: applications open, deadline = now => submitted

Jeff King writes: > On Fri, Feb 19, 2016 at 09:09:50AM +0100, Matthieu Moy wrote: > >> Hi, >> >> The deadline is tonight (19:00 UTC). I don't want to miss it, so I'll >> submit the application very soon based on >> http://git.github.io/SoC-2016-Org-Application/. > > I think we can continue to mo

GSoC 2016: Microproject

Hello everyone, I'm Mehul Jain. I'm looking for participating in GSoC 2016. I've started work on a Microproject" Teach git pull --rebase the --no-autostash" option. While looking at Git's source code I have made following observation: In the pull.c file 1. git_conf

Re: GSoC 2016: applications open, deadline = now => submission

On Fri, Feb 19, 2016 at 09:09:50AM +0100, Matthieu Moy wrote: > Hi, > > The deadline is tonight (19:00 UTC). I don't want to miss it, so I'll > submit the application very soon based on > http://git.github.io/SoC-2016-Org-Application/. I think we can continue to modify up to the deadline (at lea

Re: GSoC 2016: applications open, deadline = now => submission

Hi, The deadline is tonight (19:00 UTC). I don't want to miss it, so I'll submit the application very soon based on http://git.github.io/SoC-2016-Org-Application/. Other pages can still be modified afterwards. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: se

Re: GSoC 2016: applications open, libgit2 and git.git

Carlos Martín Nieto writes: > We still have most of the same things open as for the 2014 list. I'll > ask around to see if we have. Last year I wasn't involved in the > candidate selection but IIRC we didn't do a project as none of the > applications showed the candidates would be capable of doin

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Junio C Hamano writes: > Deciding what the 'safe' subset is must be done with a lot of > thinking by people who intimately know what implications it has to > ban each feature. I do not think it would be a good fit for a > project to give to a relatively new participant to the Git project. I hav

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Duy Nguyen writes: > On Thu, Feb 18, 2016 at 1:58 AM, Matthieu Moy > wrote: >> Feel free to start writting an idea for >> http://git.github.io/SoC-2016-Ideas/. It'd be nice to have a few more >> ideas before Friday. We can polish them later if needed. > > Probably too late now, anyway.. It's st

GSoC 2016

Hello everyone, I'm Mehul Jain. I'm looking for participating in GSoC 2016. I've started work on a Microproject" Teach git pull --rebase the --no-autostash" option. While looking at Git's source code I have made following observation: In the pull.c file 1. git_conf

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Fri, Feb 19, 2016 at 10:20 AM, Junio C Hamano wrote: > Duy Nguyen writes: > >> Probably too late now, anyway.. with David's multiple ref backend >> work, we could have a third, no-dependency backend. We can use index >> format to store refs. Then we can avoid case-sensitivity issue with >> fil

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Duy Nguyen writes: > Probably too late now, anyway.. with David's multiple ref backend > work, we could have a third, no-dependency backend. We can use index > format to store refs. Then we can avoid case-sensitivity issue with > filesystems. I'd actually vote for a ref backend that is based on

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Thu, Feb 18, 2016 at 1:58 AM, Matthieu Moy wrote: > Feel free to start writting an idea for > http://git.github.io/SoC-2016-Ideas/. It'd be nice to have a few more > ideas before Friday. We can polish them later if needed. Probably too late now, anyway.. with David's multiple ref backend work,

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Stefan Beller writes: > On Thu, Feb 18, 2016 at 12:41 AM, Lars Schneider > wrote: >>> Feel free to start writting an idea for >>> http://git.github.io/SoC-2016-Ideas/. It'd be nice to have a few more >>> ideas before Friday. We can polish them later if needed. >> >> I published my ideas here: >>

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Thu, Feb 18, 2016 at 12:41 AM, Lars Schneider wrote: >> Feel free to start writting an idea for >> http://git.github.io/SoC-2016-Ideas/. It'd be nice to have a few more >> ideas before Friday. We can polish them later if needed. > > I published my ideas here: > https://github.com/git/git.github

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Wed, 2016-02-17 at 13:33 -0800, Junio C Hamano wrote: > Jeff King writes: > > > On Wed, Feb 17, 2016 at 09:21:20PM +0100, Matthieu Moy wrote: > > > > > > I am wondering if we heard from libgit2 folks if they want us > > > > to > > > > host them (or they want to participate in GSoC at all). >

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On 17 Feb 2016, at 19:58, Matthieu Moy wrote: > Lars Schneider writes: > >> Coincidentally I started working on similar thing already (1) and I have >> lots of ideas around it. > > I guess it's time to start sharing these ideas then ;-). > > I think there's a lot to do. If we want to push th

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Jeff King writes: > On Wed, Feb 17, 2016 at 09:21:20PM +0100, Matthieu Moy wrote: > >> > I am wondering if we heard from libgit2 folks if they want us to >> > host them (or they want to participate in GSoC at all). >> >> The libgit2 mention is left from previous versions of this page. I left >>

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Wed, Feb 17, 2016 at 09:21:20PM +0100, Matthieu Moy wrote: > > I am wondering if we heard from libgit2 folks if they want us to > > host them (or they want to participate in GSoC at all). > > The libgit2 mention is left from previous versions of this page. I left > a message on their IRC chann

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Junio C Hamano writes: > Matthieu Moy writes: > >> Feel free to start writting an idea for >> http://git.github.io/SoC-2016-Ideas/. It'd be nice to have a few more >> ideas before Friday. We can polish them later if needed. > > The top of the page says it is shared between Git and libgit2; > sho

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Lars Schneider writes: > Coincidentally I started working on similar thing already (1) and I have > lots of ideas around it. I guess it's time to start sharing these ideas then ;-). I think there's a lot to do. If we want to push this idea as a GSoC project, we need: * A rough plan. We can't e

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Matthieu Moy writes: > Feel free to start writting an idea for > http://git.github.io/SoC-2016-Ideas/. It'd be nice to have a few more > ideas before Friday. We can polish them later if needed. The top of the page says it is shared between Git and libgit2; should that be really the case? We lat

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On 17 Feb 2016, at 18:24, Thomas Gummerer wrote: > On 02/10, Matthieu Moy wrote: >> Work on the application itself, and on the list of ideas. > > One potential idea: > > Make destructive git commands more safe for the user. > > Some commands (e.g. git reset --hard, git clean -f, etc.) can > p

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On 02/10, Matthieu Moy wrote: > Work on the application itself, and on the list of ideas. One potential idea: Make destructive git commands more safe for the user. Some commands (e.g. git reset --hard, git clean -f, etc.) can potentially destroy some of the users work. Store the information tha

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Hi Johannes, On Wed, Feb 17, 2016 at 2:09 PM, Johannes Schindelin wrote: > >> Then there is also git-bisect.sh with nearly 700 lines, which is also >> not as easy. > > Nothing is easy, but bisect has a much better chance to be finally > converted into a builtin: there is already a bisect--helper

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Hi Stefan, On Tue, 16 Feb 2016, Stefan Beller wrote: > I'd be interested to co-mentor a sh->C conversion. > > I think the git-rebase*.sh is a good start. > > $ wc -l git-rebase*.sh > 101 git-rebase--am.sh > 1296 git-rebase--interactive.sh > 167 git-rebase--merge.sh > 636 git-rebase.sh >

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Wed, Feb 17, 2016 at 5:34 PM, Matthieu Moy wrote: > Stefan Beller writes: > >> I'd be interested to co-mentor a sh->C conversion. >> >> I think the git-rebase*.sh is a good start. >> >> $ wc -l git-rebase*.sh >> 101 git-rebase--am.sh >> 1296 git-rebase--interactive.sh >> 167 git-rebase--m

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Stefan Beller writes: > I'd be interested to co-mentor a sh->C conversion. > > I think the git-rebase*.sh is a good start. > > $ wc -l git-rebase*.sh > 101 git-rebase--am.sh > 1296 git-rebase--interactive.sh > 167 git-rebase--merge.sh > 636 git-rebase.sh > 2200 total > > So start with reb

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Sat, Feb 13, 2016 at 3:21 AM, Matthieu Moy wrote: > Jeff King writes: > >> On Fri, Feb 12, 2016 at 08:10:34AM +0100, Matthieu Moy wrote: >> >>> So, that makes it 4 possible co-mentors, i.e. 2 potential slots. Not >>> much, but it starts looking like last year ... ;-). >>> >>> Peff, would you b

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Jeff King writes: > On Fri, Feb 12, 2016 at 08:10:34AM +0100, Matthieu Moy wrote: > >> So, that makes it 4 possible co-mentors, i.e. 2 potential slots. Not >> much, but it starts looking like last year ... ;-). >> >> Peff, would you be willing to co-admin with me (that would be cool, you >> are

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Fri, Feb 12, 2016 at 08:04:46AM -0500, Jeff King wrote: > The biggest task there is getting the application together. I went > through the account creation steps at the site (which is different this > year), and the application questions are: > [...] We also need to fill out our profile. Those

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On Fri, Feb 12, 2016 at 08:10:34AM +0100, Matthieu Moy wrote: > So, that makes it 4 possible co-mentors, i.e. 2 potential slots. Not > much, but it starts looking like last year ... ;-). > > Peff, would you be willing to co-admin with me (that would be cool, you > are the one with most experience

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Lars Schneider writes: > I don't know what level of Git development knowledge and what amount of time > is necessary but I would be available as junior co-mentor :-) AFAICT, you don't have much experience with Git's codebase itself (if I don't count git-p4 as "Git itself"), but you've already be

Re: GSoC 2016: applications open, deadline = Fri, 19/2

On 12 Feb 2016, at 08:10, Matthieu Moy wrote: > Christian Couder writes: > >> Hi, >> >> On Wed, Feb 10, 2016 at 10:31 AM, Matthieu Moy >> wrote: >>> >>> So, the first question is: are there volunteers to be GSoC mentors this >>> year? >> >> I can co-mentor this year too, with you or someon

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Christian Couder writes: > Hi, > > On Wed, Feb 10, 2016 at 10:31 AM, Matthieu Moy > wrote: >> >> So, the first question is: are there volunteers to be GSoC mentors this >> year? > > I can co-mentor this year too, with you or someone else. > With you I think it will work out even if you have less

Re: GSoC 2016: applications open, deadline = Fri, 19/2

Hi, On Wed, Feb 10, 2016 at 10:31 AM, Matthieu Moy wrote: > > So, the first question is: are there volunteers to be GSoC mentors this > year? I can co-mentor this year too, with you or someone else. With you I think it will work out even if you have less time than last year. Best, Christian. --

  1   2   >