Hi,
I published a new blog post about this week. You can read it here:
https://blog.pa1ch.fr/posts/2018/05/12/en/gsoc2018-week-2.html
Please tell me what you think about it :)
Cheers,
Alban
.html
Cheers,
Alban Gruin
Le 25/04/2018 à 14:53, Ulrich Windl a écrit :
> Hi!
>
> This is for git 2.13.6, and it may be an FAQ or frequent feature request.
> Anyway:
> I'm new to Java, and writing my first project using Git, I found that "git
> diff" only reports the class in the diff context, but not the method (as
convert git-stash
> into a builtin.
>
> Alban Gruin and Pratik Karki want to convert parts of git-rebase into
> a builtin. Both are mentored by Christian and myself.
>
> The slots were just announced today, please join me in welcoming them
> to the Git mailing list! (Although you may
the
mailing list.
ABOUT ME
My name is Alban Gruin. I am an undergraduate at the Paul Sabatier
University in Toulouse, France, where I have been studying Computer
Sciences for a year and a half. My timezone is UTC+02:00.
I have been programming in C for the last 5 years. I learned using
o fix it.
* Add an option to include the patch in the message of commits to be
reworded, as proposed by Ævar Arnfjörð Bjarmason[4].
ABOUT ME
My name is Alban Gruin. I am an undergraduate at the Paul Sabatier
University in Toulouse, France, where I have been studying Computer
Sciences for a yea
Hi Johannes,
Le mardi 20 mars 2018 17:29:28 CET, vous avez écrit :
> > Weeks 1 & 2 — May 14, 2018 – May 28, 2018
> > First, I would refactor --preserve-merges in its own shell script, as
> > described in Dscho’s email.
>
> Could you go into detail a bit here? Like, describe what parts of the
>
018
In the second half of July, I would look for bugs in the new code, test it,
and improve its coverage.
Weeks 12 — July 30, 2018 – August 5, 2018
In the last week, I would polish the code where needed, in order to improve
for performance or to make the code more readable.
ABOUT ME
My nam
Le 07/03/2018 à 22:56, Alban Gruin a écrit :
> Hi,
>
> I was reading the email related to the "convert interactive rebase to C"
> idea[1], and I have a few questions about it:
Hi,
I’m writing to you again, in order to have some more information about
the "conv
Hi,
I was reading the email related to the "convert interactive rebase to C"
idea[1], and I have a few questions about it:
> So the first goal would be to retire git-rebase--interactive.sh. For that
> to happen, --root needs to be supported first.
Combining rebase -i and --root seems to work
and operators, according to the go specification.
Signed-off-by: Alban Gruin <alban.gr...@gmail.com>
---
Documentation/gitattributes.txt | 2 ++
t/t4018-diff-funcname.sh| 1 +
t/t4018/golang-complex-function | 8
t/t4018/golang-func | 4
t/t4018/golang-int
Le 28/02/2018 à 23:32, Junio C Hamano a écrit :
> Eric Sunshine <sunsh...@sunshineco.com> writes:
>
>> On Wed, Feb 28, 2018 at 5:17 PM, Alban Gruin <alban.gr...@gmail.com> wrote:
>>> Yes, but I can split the line like that:
>>>
>>> % cat >
Le 28/02/2018 à 23:00, Eric Sunshine a écrit :
> On Wed, Feb 28, 2018 at 4:31 PM, Alban Gruin <alban.gr...@gmail.com> wrote:
>>>> diff --git a/userdiff.c b/userdiff.c
>>>> @@ -38,6 +38,15 @@ IPATTERN("fortran",
>>>> +PATTERNS("golang&quo
>> diff --git a/userdiff.c b/userdiff.c
>> @@ -38,6 +38,15 @@ IPATTERN("fortran",
>> +PATTERNS("golang",
>> +/* Functions */
>> +"^[ \t]*(func[ \t]*.*(\\{[ \t]*)?)\n"
>
> Why is the brace (and possible following whitespace) optional?
> Considering that the language demands that
, floats, complex
numbers and operators, according to the go specification.
Signed-off-by: Alban Gruin <alban.gr...@gmail.com>
---
Documentation/gitattributes.txt | 2 ++
t/t4018-diff-funcname.sh| 1 +
t/t4018/golang-complex-function | 8
t/t4018/golang-func | 4 +
301 - 315 of 315 matches
Mail list logo
