On 21 May 2018 01:03:22 GMT+05:30, Paul-Sebastian Ungureanu
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 mi
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 k
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, m
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, whic
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
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-inb
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
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
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. Th
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
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 wo
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 t
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 be
13 matches
Mail list logo