[GSoC] A blog about 'git stash' project

[GSoC] A blog about 'git stash' project

[Paul-Sebastian Ungureanu]

Hello everybody,

The community bonding period started. It is well known that for a 
greater rate of success, it is recommended to send weekly reports 
regarding project status. But, what would be a good form for such a 
report? I, for one, think that starting a blog is one of the best 
options because all the content will be stored in one place. Without 
further ado, I would like you to present my blog [1].

Any feedback is greatly appreciated! Thank you!

[1]
https://ungps.github.io/

Best regards,
Paul Ungureanu

Re: [GSoC] A blog about 'git stash' project

[Johannes Schindelin]

Hi Paul,

On Fri, 4 May 2018, Paul-Sebastian Ungureanu wrote:

> The community bonding period started. It is well known that for a
> greater rate of success, it is recommended to send weekly reports
> regarding project status.  But, what would be a good form for such a
> report? I, for one, think that starting a blog is one of the best
> options because all the content will be stored in one place. Without
> further ado, I would like you to present my blog [1].
> 
> Any feedback is greatly appreciated! Thank you!
> 
> [1]
> https://ungps.github.io/

Looks great!

Maybe also mention that you hang out on IRC occasionally, in case anybody
wants to tell you just how awesome a contributor you are?

Ciao,
Dscho

Re: [GSoC] A blog about 'git stash' project

[Paul-Sebastian Ungureanu]

Hello Dscho,

On 04.05.2018 01:10, Johannes Schindelin wrote:
> Hi Paul,
> 
> On Fri, 4 May 2018, Paul-Sebastian Ungureanu wrote:
> 
>> The community bonding period started. It is well known that for a
>> greater rate of success, it is recommended to send weekly reports
>> regarding project status.  But, what would be a good form for such a
>> report? I, for one, think that starting a blog is one of the best
>> options because all the content will be stored in one place. Without
>> further ado, I would like you to present my blog [1].
>>
>> Any feedback is greatly appreciated! Thank you!
>>
>> [1]
>> https://ungps.github.io/
> 
> Looks great!
> 
> Maybe also mention that you hang out on IRC occasionally, in case anybody
> wants to tell you just how awesome a contributor you are?
> 
> Ciao,
> Dscho
> 

Thanks for the kind words and for mentoring me. It really means a lot to 
me seeing that my work is appreciated by professionals like you. It is a 
great confidence boost. I will definitely add a paragraph about IRC.

Best,
Paul Ungureanu

Re: [GSoC] A blog about 'git stash' project

[Kaartic Sivaraam]

[-- Attachment #1.1: Type: text/plain, Size: 2371 bytes --]

Hi Sebi,

On Friday 04 May 2018 03:18 AM, Paul-Sebastian Ungureanu wrote:
> Hello everybody,
> 
> The community bonding period started. It is well known that for a
> greater rate of success, it is recommended to send weekly reports
> regarding project status. But, what would be a good form for such a
> report? I, for one, think that starting a blog is one of the best
> options because all the content will be stored in one place. Without
> further ado, I would like you to present my blog [1].
> 
> Any feedback is greatly appreciated! Thank you!
> 

The blog looks pretty well written. I also read your proposal. It also
seems to be pretty much well written. I like the way you explain things.
Particularly, you seem to be explaining the problem and the way you're
about to approach it well. The plan seems pretty good.

I just thought of suggesting one thing which might possibly be
redundant. I think you're aware of the fact that the Git project has
Travis-CI builds enabled[1] which you could take advantage of to ensure
your changes pass in various text environments.

If you're interested in testing your changes (which I suspect you are),
you might also be interested in 'git-test'[2], a tool built by Michael
Haggerty. Unlike the Travis-CI tests which test only the tip of the
change, 'git-test' would help you ensure that every single commit you
make doesn't break the test suite (which is both a nice thing and is
expected here).

Sorry for the off-topic info about the tests in this mail :-)

Hope you're able to achieve your goal as planned and have a great time
during this summer of code!


References:
[1]:
https://github.com/git/git/blob/master/Documentation/SubmittingPatches#L70

[2]: https://github.com/mhagger/git-test


Regards,
Kaartic

QUOTE:

“The most valuable person on any team is the person who makes everyone
else on the team more valuable, not the person who knows the most.”

      - Joel Spolsky

KIND NOTE TO THE NATIVE ENGLISH SPEAKER:

As I'm not a native English speaker myself, there might be mistaeks in
my usage of English. I apologise for any mistakes that I make.

It would be "helpful" if you take the time to point out the mistakes.

It would be "super helpful" if you could provide suggestions about how
to correct those mistakes.

Thanks in advance!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [GSoC] A blog about 'git stash' project

[Paul-Sebastian Ungureanu]

Hello,

On 06.05.2018 16:22, Kaartic Sivaraam wrote:
> The blog looks pretty well written. I also read your proposal. It also
> seems to be pretty much well written. I like the way you explain things.
> Particularly, you seem to be explaining the problem and the way you're
> about to approach it well. The plan seems pretty good.

Thank you a lot!

> I just thought of suggesting one thing which might possibly be
> redundant. I think you're aware of the fact that the Git project has
> Travis-CI builds enabled[1] which you could take advantage of to ensure
> your changes pass in various text environments.
> 
> If you're interested in testing your changes (which I suspect you are),
> you might also be interested in 'git-test'[2], a tool built by Michael
> Haggerty. Unlike the Travis-CI tests which test only the tip of the
> change, 'git-test' would help you ensure that every single commit you
> make doesn't break the test suite (which is both a nice thing and is
> expected here).

I heard of it and used it a couple of times (for the micro-project and 
some other patch).

> Sorry for the off-topic info about the tests in this mail :-)

You shouldn't be sorry. Nothing was off-topic; I found everything you 
said to be helpful! Every feedback is welcomed!

> Hope you're able to achieve your goal as planned and have a great time
> during this summer of code!

Thank you one more time! I know it will be a good summer.

Best,
Paul Ungureanu

Re: [GSoC] A blog about 'git stash' project

[Kaartic Sivaraam]

[-- Attachment #1.1: Type: text/plain, Size: 1491 bytes --]

Hi Sebi,

I thought of pointing you to one of the issues with the current
implementation of 'git stash' which you could probably fix while porting
it to C. It's about stashing untracked files.

You could find more information about it in the following mailing list
thread:
	https://public-inbox.org/git/1505626069.9625.6.camel@gmail.com/


-- 
Sivaraam

QUOTE:

“The most valuable person on any team is the person who makes everyone
else on the team more valuable, not the person who knows the most.”

      - John Sonmez


Sivaraam?

You possibly might have noticed that my signature recently changed from
'Kaartic' to 'Sivaraam' both of which are parts of my name. I find the
new signature to be better for several reasons one of which is that the
former signature has a lot of ambiguities in the place I live as it is a
common name (NOTE: it's not a common spelling, just a common name). So,
I switched signatures before it's too late.

That said, I won't mind you calling me 'Kaartic' if you like it [of
course ;-)]. You can always call me using either of the names.


KIND NOTE TO THE NATIVE ENGLISH SPEAKER:

As I'm not a native English speaker myself, there might be mistaeks in
my usage of English. I apologise for any mistakes that I make.

It would be "helpful" if you take the time to point out the mistakes.

It would be "super helpful" if you could provide suggestions about how
to correct those mistakes.

Thanks in advance!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [GSoC] A blog about 'git stash' project

[Kaartic Sivaraam]

[-- Attachment #1.1: Type: text/plain, Size: 1697 bytes --]

On Thursday 17 May 2018 12:28 PM, Kaartic Sivaraam wrote:
> Hi Sebi,
> 
> I thought of pointing you to one of the issues with the current
> implementation of 'git stash' which you could probably fix while porting
> it to C.
>
> ...
> 

Forgot to mention about another issue, which I consider to be a bug. I
have elaborated about it in the following mailing list email.

	https://public-inbox.org/git/aa43f1ff-9095-fb4d-43bc-bf8283b7dabb@gmail.com/

Unfortunately, it didn't receive any replies. See, if you could do
something about it.


-- 
Sivaraam

QUOTE:

“The most valuable person on any team is the person who makes everyone
else on the team more valuable, not the person who knows the most.”

      - John Sonmez


Sivaraam?

You possibly might have noticed that my signature recently changed from
'Kaartic' to 'Sivaraam' both of which are parts of my name. I find the
new signature to be better for several reasons one of which is that the
former signature has a lot of ambiguities in the place I live as it is a
common name (NOTE: it's not a common spelling, just a common name). So,
I switched signatures before it's too late.

That said, I won't mind you calling me 'Kaartic' if you like it [of
course ;-)]. You can always call me using either of the names.


KIND NOTE TO THE NATIVE ENGLISH SPEAKER:

As I'm not a native English speaker myself, there might be mistaeks in
my usage of English. I apologise for any mistakes that I make.

It would be "helpful" if you take the time to point out the mistakes.

It would be "super helpful" if you could provide suggestions about how
to correct those mistakes.

Thanks in advance!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [GSoC] A blog about 'git stash' project

[Johannes Schindelin]

Hi Kaartic,

> On Thursday 17 May 2018 12:28 PM, Kaartic Sivaraam wrote:
> 
> > I thought of pointing you to one of the issues with the current
> > implementation of 'git stash' which you could probably fix while
> > porting it to C.
> >
> > ...
> > 
> 
> Forgot to mention about another issue, which I consider to be a bug. I
> have elaborated about it in the following mailing list email.
> 
> 	https://public-inbox.org/git/aa43f1ff-9095-fb4d-43bc-bf8283b7dabb@gmail.com/
> 
> Unfortunately, it didn't receive any replies. See, if you could do
> something about it.

I have great empathy for the desire to see these bugs fixed. The
conversion must come first, though, and in the interest of making it
easier on me and other reviewers, I must insist on keeping the conversion
free of any changes, much in the way as we try to avoid evil merges (i.e.
merge commits that introduce changes that were not present in any of their
parents).

Depending how the conversion goes, I could imagine that there might be
plenty of time to do fun stuff on top, such as fixes for the bugs you
mentioned.

Ciao,
Johannes

Re: [GSoC] A blog about 'git stash' project

[Kaartic Sivaraam]

[-- Attachment #1.1: Type: text/plain, Size: 2082 bytes --]

On Thursday 17 May 2018 02:39 PM, Johannes Schindelin wrote:
> I have great empathy for the desire to see these bugs fixed. The
> conversion must come first, though, and in the interest of making it
> easier on me and other reviewers, I must insist on keeping the conversion
> free of any changes, much in the way as we try to avoid evil merges (i.e.
> merge commits that introduce changes that were not present in any of their
> parents).
> 

Of course, the conversion should be separate from the bug fixes :-)

When I mentioned "while porting it to C", I actually meant the "thought
process of creating a foundation for `git-stash` in C". I thought
hinting at some of the existing and unsolved `git-stash` bugs would
allow the person who would be doing the port of `git-stash` to C to
consider how to avoid this while implementing the basic foundation. I
should have been more explicit about this in my previous mails.


-- 
Sivaraam

QUOTE:

“The most valuable person on any team is the person who makes everyone
else on the team more valuable, not the person who knows the most.”

      - John Sonmez


Sivaraam?

You possibly might have noticed that my signature recently changed from
'Kaartic' to 'Sivaraam' both of which are parts of my name. I find the
new signature to be better for several reasons one of which is that the
former signature has a lot of ambiguities in the place I live as it is a
common name (NOTE: it's not a common spelling, just a common name). So,
I switched signatures before it's too late.

That said, I won't mind you calling me 'Kaartic' if you like it [of
course ;-)]. You can always call me using either of the names.


KIND NOTE TO THE NATIVE ENGLISH SPEAKER:

As I'm not a native English speaker myself, there might be mistaeks in
my usage of English. I apologise for any mistakes that I make.

It would be "helpful" if you take the time to point out the mistakes.

It would be "super helpful" if you could provide suggestions about how
to correct those mistakes.

Thanks in advance!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [GSoC] A blog about 'git stash' project

[Paul-Sebastian Ungureanu]

Hi

On 17.05.2018 13:29, Kaartic Sivaraam wrote:
> On Thursday 17 May 2018 02:39 PM, Johannes Schindelin wrote:
>> I have great empathy for the desire to see these bugs fixed. The
>> conversion must come first, though, and in the interest of making it
>> easier on me and other reviewers, I must insist on keeping the conversion
>> free of any changes, much in the way as we try to avoid evil merges (i.e.
>> merge commits that introduce changes that were not present in any of their
>> parents).
>>
> 
> Of course, the conversion should be separate from the bug fixes :-)
> 
> When I mentioned "while porting it to C", I actually meant the "thought
> process of creating a foundation for `git-stash` in C". I thought
> hinting at some of the existing and unsolved `git-stash` bugs would
> allow the person who would be doing the port of `git-stash` to C to
> consider how to avoid this while implementing the basic foundation. I
> should have been more explicit about this in my previous mails.
> 

Thank you! I will keep in mind to fix those bugs. I actually wrote a 
short paragraph about one of them (the one regarding -p option) on the 
blog (the first post).

Best,
Paul

Re: [GSoC] A blog about 'git stash' project

[Kaartic Sivaraam]

On 21 May 2018 01:03:22 GMT+05:30, Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com> wrote:
>
> I actually wrote a 
>short paragraph about one of them (the one regarding -p option) on the 
>blog (the first post).
>

That's interesting. I didn't realise that you wrote about one of the bugs in your blog. I might have missed it, somehow.

Anyhow, it happens to me all the time ;-)
-- 
Sivaraam

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [GSoC] A blog about 'git stash' project

[Taylor Blau]

On Fri, May 04, 2018 at 12:48:21AM +0300, Paul-Sebastian Ungureanu wrote:
> Hello everybody,
>
> The community bonding period started. It is well known that for a greater
> rate of success, it is recommended to send weekly reports regarding project
> status. But, what would be a good form for such a report? I, for one, think
> that starting a blog is one of the best options because all the content will
> be stored in one place. Without further ado, I would like you to present my
> blog [1].

Hi Paul, and welcome to Git! I am looking forward to reading your
patches and any additional writing posted on your blog.

> Any feedback is greatly appreciated! Thank you!

Do you have a RSS feed that I can consume in a feed reader?

> [1]
> https://ungps.github.io/
>
> Best regards,
> Paul Ungureanu

Thanks,
Taylor

Re: [GSoC] A blog about 'git stash' project

[Paul-Sebastian Ungureanu]

Hello,

On 08.05.2018 07:00, Taylor Blau wrote:
> On Fri, May 04, 2018 at 12:48:21AM +0300, Paul-Sebastian Ungureanu wrote:
>> Hello everybody,
>>
>> The community bonding period started. It is well known that for a greater
>> rate of success, it is recommended to send weekly reports regarding project
>> status. But, what would be a good form for such a report? I, for one, think
>> that starting a blog is one of the best options because all the content will
>> be stored in one place. Without further ado, I would like you to present my
>> blog [1].
> 
> Hi Paul, and welcome to Git! I am looking forward to reading your
> patches and any additional writing posted on your blog.

It is a pleasure to be here. Thank you!

>> Any feedback is greatly appreciated! Thank you!
> 
> Do you have a RSS feed that I can consume in a feed reader?

Yes. It can be found here [1].

[1]
https://ungps.github.io/atom.xml
Best,
Paul