All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [GSoC] A blog about 'git stash' project
Date: Sun, 20 May 2018 22:33:22 +0300	[thread overview]
Message-ID: <e0029f5e-87eb-7531-c32d-9a58469faaa5@gmail.com> (raw)
In-Reply-To: <1729567e-3b95-ab37-d845-1980795542b0@gmail.com>

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

  reply	other threads:[~2018-05-20 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 21:48 [GSoC] A blog about 'git stash' project Paul-Sebastian Ungureanu
2018-05-03 22:10 ` Johannes Schindelin
2018-05-04 21:48   ` Paul-Sebastian Ungureanu
2018-05-06 13:22 ` Kaartic Sivaraam
2018-05-07 16:37   ` Paul-Sebastian Ungureanu
2018-05-17  6:58     ` Kaartic Sivaraam
2018-05-17  7:11       ` Kaartic Sivaraam
2018-05-17  9:09         ` Johannes Schindelin
2018-05-17 10:29           ` Kaartic Sivaraam
2018-05-20 19:33             ` Paul-Sebastian Ungureanu [this message]
2018-05-23  3:20               ` Kaartic Sivaraam
2018-05-08  4:00 ` Taylor Blau
2018-05-08 21:19   ` Paul-Sebastian Ungureanu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e0029f5e-87eb-7531-c32d-9a58469faaa5@gmail.com \
    --to=ungureanupaulsebastian@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.