Am 2017-05-15 um 17:19 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 17:04 +0200, Michael Osipov wrote:
Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
...
I actually did:
https://mail-archives.apache.org/mod_mbox/hc-dev/201
Am 2017-05-15 um 17:19 schrieb Gary Gregory:
On Mon, May 15, 2017 at 8:04 AM, Michael Osipov wrote:
Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
...
Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
What benefit do you ha
On Mon, 2017-05-15 at 17:04 +0200, Michael Osipov wrote:
> Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
> > On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
> > > >
> >
> >
...
> I actually did:
> https://mail-archives.apache.org/mod_mbox/hc-dev/201705.mbox/%3C01066
> 1f8-4e15-01
On Mon, May 15, 2017 at 8:04 AM, Michael Osipov wrote:
> Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
>
>> On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
>>
>>>
>> ...
>>
>>
>> Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
>>> What benefit do you have if it is hard to foll
Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
...
Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
What benefit do you have if it is hard to follow the code paths? How
much is "good" code worth if you don't have proper documenta
On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
> >
...
> Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
> What benefit do you have if it is hard to follow the code paths? How
> much is "good" code worth if you don't have proper documentation?
> Even
> if you have to constantly cl
Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 15:18 +0200, Michael Osipov wrote:
...
Am 2017-05-15 um 15:05 schrieb Oleg Kalnichevski:
I have _no_ intention of policing other committers. It is
emotionally
cheaper for me to take time to clean things up and than to
On Mon, 2017-05-15 at 15:18 +0200, Michael Osipov wrote:
> >
...
> Am 2017-05-15 um 15:05 schrieb Oleg Kalnichevski:
> > I have _no_ intention of policing other committers. It is
> > emotionally
> > cheaper for me to take time to clean things up and than to hold all
> > those conversations abou
Am 2017-05-15 um 15:05 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 14:58 +0200, Michael Osipov wrote:
Am 2017-05-15 um 13:13 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 11:54 +0200, Julian Sedding wrote:
Force pushing is considered a bad practice in Git for good
reasons,
thus rewriti
On Mon, 2017-05-15 at 14:58 +0200, Michael Osipov wrote:
> Am 2017-05-15 um 13:13 schrieb Oleg Kalnichevski:
> > On Mon, 2017-05-15 at 11:54 +0200, Julian Sedding wrote:
> > > Force pushing is considered a bad practice in Git for good
> > > reasons,
> > > thus rewriting history of published branche
Am 2017-05-15 um 13:13 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 11:54 +0200, Julian Sedding wrote:
Force pushing is considered a bad practice in Git for good reasons,
thus rewriting history of published branches is IMHO a no-go. It
makes
everybody's life harder (and developers less exper
On Mon, 2017-05-15 at 11:54 +0200, Julian Sedding wrote:
> Force pushing is considered a bad practice in Git for good reasons,
> thus rewriting history of published branches is IMHO a no-go. It
> makes
> everybody's life harder (and developers less experienced with Git may
> not be able to integrat
Am 2017-05-15 um 11:54 schrieb Julian Sedding:
Force pushing is considered a bad practice in Git for good reasons,
thus rewriting history of published branches is IMHO a no-go. It makes
everybody's life harder (and developers less experienced with Git may
not be able to integrate the rewritten hi
Force pushing is considered a bad practice in Git for good reasons,
thus rewriting history of published branches is IMHO a no-go. It makes
everybody's life harder (and developers less experienced with Git may
not be able to integrate the rewritten history at all).
Don't get me wrong. I do a lot of
On Thu, 2017-05-11 at 00:00 +0200, Michael Osipov wrote:
> Am 2017-05-10 um 23:48 schrieb Oleg Kalnichevski:
> > On Wed, 2017-05-10 at 23:25 +0200, Michael Osipov wrote:
> >
> >
...
> > I am not sure I understand what you mean by git apply.
> >
> > Can we go back to what appears to be the only
Am 2017-05-10 um 23:48 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 23:25 +0200, Michael Osipov wrote:
...
But your answer is contrary to your previous statement -- cherry-
picking
shouldn't be a fuzz with two different repos. Can you explain
why?
My understanding is that cherry picking
On Wed, 2017-05-10 at 23:25 +0200, Michael Osipov wrote:
...
> > > But your answer is contrary to your previous statement -- cherry-
> > > picking
> > > shouldn't be a fuzz with two different repos. Can you explain
> > > why?
> > >
> >
> > My understanding is that cherry picking is not possible
Am 2017-05-10 um 23:19 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 22:00 +0200, Michael Osipov wrote:
Am 2017-05-10 um 21:54 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:45 +0200, Michael Osipov wrote:
This will a problem anyway because all paths change (package
names,
etc.). Hope
On Wed, 2017-05-10 at 22:00 +0200, Michael Osipov wrote:
> Am 2017-05-10 um 21:54 schrieb Oleg Kalnichevski:
> > On Wed, 2017-05-10 at 21:45 +0200, Michael Osipov wrote:
> > >
> > > This will a problem anyway because all paths change (package
> > > names,
> > > etc.). Hopefully Git's similarity al
Am 2017-05-10 um 21:54 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:45 +0200, Michael Osipov wrote:
This will a problem anyway because all paths change (package names,
etc.). Hopefully Git's similarity algorithm can detect this.
No, it is not. Git is that great. It always amazes me ho
On Wed, 2017-05-10 at 21:45 +0200, Michael Osipov wrote:
>
> This will a problem anyway because all paths change (package names,
> etc.). Hopefully Git's similarity algorithm can detect this.
>
No, it is not. Git is that great. It always amazes me how intelligent
Git when it comes to merging st
Am 2017-05-10 um 21:42 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:27 +0200, Michael Osipov wrote:
Am 2017-05-10 um 21:16 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote:
Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 11:15 -
On Wed, 2017-05-10 at 21:27 +0200, Michael Osipov wrote:
> Am 2017-05-10 um 21:16 schrieb Oleg Kalnichevski:
> > On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote:
> > > Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
> > > > On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote:
> > > > >
On Wed, May 10, 2017 at 12:27 PM, Michael Osipov
wrote:
> Am 2017-05-10 um 21:16 schrieb Oleg Kalnichevski:
>
>> On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote:
>>
>>> Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
>>>
On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote:
>
Am 2017-05-10 um 21:16 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote:
Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote:
On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski
wrote:
...
One person
If the committer squashes their commits *before* pushing then history
is maintained.
On 10 May 2017 at 20:16, Oleg Kalnichevski wrote:
> On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote:
>> Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
>> > On Wed, 2017-05-10 at 11:15 -0700, Gary Grego
On Wed, 2017-05-10 at 21:07 +0200, Michael Osipov wrote:
> Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
> > On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote:
> > > On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski > > .org
> > > >
> > >
> > > wrote:
> > >
> > > > ...
> > > >
> > >
Am 2017-05-10 um 20:52 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote:
On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski
wrote:
...
One personal request. Do you think you could try to make your
commits
less granular and combine logically related change
On Wed, 2017-05-10 at 11:15 -0700, Gary Gregory wrote:
> On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski >
> wrote:
>
> > ...
> >
> >
> > > > One personal request. Do you think you could try to make your
> > > > commits
> > > > less granular and combine logically related changes into larger
On Wed, 2017-05-10 at 09:51 -0700, Gary Gregory wrote:
> Can you rename trunk to master and then give the green light?
>
Done. SVN trunk pushed to remote as master and remote trunk deleted.
Oleg
> Gary
>
> On Wed, May 10, 2017 at 12:59 AM, Oleg Kalnichevski >
> wrote:
>
> > Folks
> >
> > P
I've blow away my local SVN copy, checked out git trunk and it builds :-)
Gary
On Wed, May 10, 2017 at 12:59 AM, Oleg Kalnichevski
wrote:
> Folks
>
> Please switch your local HttpCore repositories from SVN to the new Git
> repo:
>
> https://git-wip-us.apache.org/repos/asf/httpcomponents-core.gi
On Wed, May 10, 2017 at 10:13 AM, Oleg Kalnichevski
wrote:
> ...
>
>
> > > One personal request. Do you think you could try to make your
> > > commits
> > > less granular and combine logically related changes into larger
> > > change
> > > sets?
> > >
> >
> > Old habits die hard. Git might indeed
...
> > One personal request. Do you think you could try to make your
> > commits
> > less granular and combine logically related changes into larger
> > change
> > sets?
> >
>
> Old habits die hard. Git might indeed make this better. If you want
> to add
> this to the style guideline on the si
Can you rename trunk to master and then give the green light?
Gary
On Wed, May 10, 2017 at 12:59 AM, Oleg Kalnichevski
wrote:
> Folks
>
> Please switch your local HttpCore repositories from SVN to the new Git
> repo:
>
> https://git-wip-us.apache.org/repos/asf/httpcomponents-core.git
>
> Please
On Wed, May 10, 2017 at 12:59 AM, Oleg Kalnichevski
wrote:
> Folks
>
> Please switch your local HttpCore repositories from SVN to the new Git
> repo:
>
> https://git-wip-us.apache.org/repos/asf/httpcomponents-core.git
>
> Please try to not commit to SVN while it is being set to read-only
> mode.
On Wed, 2017-05-10 at 16:18 +0200, Michael Osipov wrote:
> Am 2017-05-10 um 09:59 schrieb Oleg Kalnichevski:
> >
> > I collected all your latest SVN commits and pushed them to the Git
> > repo. Nothing should have been lost.
> >
> > One personal request. Do you think you could try to make your
>
Am 2017-05-10 um 09:59 schrieb Oleg Kalnichevski:
I collected all your latest SVN commits and pushed them to the Git
repo. Nothing should have been lost.
One personal request. Do you think you could try to make your commits
less granular and combine logically related changes into larger change
37 matches
Mail list logo
