I am in favour of using a single repository and branches (with a clean
convention). Having a repo per version IMHO sends the wrong message,
namely that the new version is completely different.
Again IMHO, we should strive to improve our backwards compatibility
with version 6.x (with regard to 5.x)
On Mon, 2017-05-15 at 10:09 +0200, Julian Sedding wrote:
> I am in favour of using a single repository and branches (with a
> clean
> convention). Having a repo per version IMHO sends the wrong message,
> namely that the new version is completely different.
>
Hi Julian
I believe this idea is off
[
https://issues.apache.org/jira/browse/HTTPCORE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010201#comment-16010201
]
Oleg Kalnichevski commented on HTTPCORE-466:
Sure. Fair enough. Would you li
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
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
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
On 12/05/2017 21:38 +0200, Oleg Kalnichevski wrote:
> You are compiling the source with Java 1.8, are you not? HttpClient 5.0
> still requires Java 1.7, which is more lenient about Javadoc content.
>
> Oleg
Yes I do.
Filipp
-
T
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 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 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 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 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 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
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki"
for change notification.
The "GitPoliciesAndPractices" page has been changed by MichaelOsipov:
https://wiki.apache.org/HttpComponents/GitPoliciesAndPractices
Comment:
Prelimary Git rules
New page:
This
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, 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
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
Dear wiki user,
You have subscribed to a wiki page "Httpcomponents Wiki" for change
notification.
The page "GitGuidelines" has been renamed from "GitPoliciesAndPractices" by
MichaelOsipov:
https://wiki.apache.org/HttpComponents/GitGuidelines
Comment:
Rename idea on the dev mailing list
-
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
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki"
for change notification.
The "GitGuidelines" page has been changed by MichaelOsipov:
https://wiki.apache.org/HttpComponents/GitGuidelines?action=diff&rev1=3&rev2=4
Comment:
Update points
## page was
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
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki"
for change notification.
The "GitGuidelines" page has been changed by MichaelOsipov:
https://wiki.apache.org/HttpComponents/GitGuidelines?action=diff&rev1=4&rev2=5
1. Never rewrite (rebase) histor
Hi Oleg
On Mon, May 15, 2017 at 11:06 AM, Oleg Kalnichevski wrote:
> On Mon, 2017-05-15 at 10:09 +0200, Julian Sedding wrote:
>> I am in favour of using a single repository and branches (with a
>> clean
>> convention). Having a repo per version IMHO sends the wrong message,
>> namely that the new
Hi,
Thank you for kicking off this thread.
I do not think "/" is good enough. At least when I tried
it, EGit would not let me create a branch in a branch which makes sense.
Which is what I used dev/4.4.x/HTTPCORE-466 in the HttpCore Git repo.
Gary
-- Forwarded message --
From
Folks,
I have updated the link based on the input and put it onto the wiki:
https://wiki.apache.org/HttpComponents/GitGuidelines
Here is verbatim copy:
= Typical Issue Workflow =
1. Branch off master ({{{git checkout -b / master}}})
where {{{}}} is the branch you are going to apply the fix, e
I wonder of all the branches that are effectively temporary should be in a
"temp/" root to make it obvious this is short term like my
dev/4.4.x/HTTPCORE-466? Not great, but maybe less confusing?
Gary
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov wrote:
> Folks,
>
> I have updated the link bas
Am 2017-05-15 um 18:34 schrieb Gary Gregory:
Hi,
Thank you for kicking off this thread.
I do not think "/" is good enough. At least when I tried
it, EGit would not let me create a branch in a branch which makes sense.
Which is what I used dev/4.4.x/HTTPCORE-466 in the HttpCore Git repo.
This
On Mon, May 15, 2017 at 10:43 AM, Gary Gregory wrote:
> Altassian has a plugin to handle (7) IIRC, we use something like that at
> work but for SVN. The plugin links a JIRA ticket to commits if the commit
> message includes the string [JIRA-ID]. There is also Altassian FishEye.
>
Gary,
Think you
Altassian has a plugin to handle (7) IIRC, we use something like that at
work but for SVN. The plugin links a JIRA ticket to commits if the commit
message includes the string [JIRA-ID]. There is also Altassian FishEye.
Gary
On Mon, May 15, 2017 at 9:34 AM, Gary Gregory
wrote:
> Hi,
>
> Thank yo
Am 2017-05-15 um 18:43 schrieb Gary Gregory:
Altassian has a plugin to handle (7) IIRC, we use something like that at
work but for SVN. The plugin links a JIRA ticket to commits if the commit
message includes the string [JIRA-ID]. There is also Altassian FishEye.
I aware of that plugin. In fact
Am 2017-05-15 um 18:59 schrieb Michael Osipov:
Am 2017-05-15 um 18:43 schrieb Gary Gregory:
Altassian has a plugin to handle (7) IIRC, we use something like that at
work but for SVN. The plugin links a JIRA ticket to commits if the commit
message includes the string [JIRA-ID]. There is also Alta
Am 2017-05-15 um 18:39 schrieb Gary Gregory:
I wonder of all the branches that are effectively temporary should be in a
"temp/" root to make it obvious this is short term like my
dev/4.4.x/HTTPCORE-466? Not great, but maybe less confusing?
I don't like that idea because you will never be able t
On Mon, May 15, 2017 at 9:45 AM, Michael Osipov wrote:
> Am 2017-05-15 um 18:39 schrieb Gary Gregory:
>
>> I wonder of all the branches that are effectively temporary should be in a
>> "temp/" root to make it obvious this is short term like my
>> dev/4.4.x/HTTPCORE-466? Not great, but maybe less
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov wrote:
> Folks,
>
> I have updated the link based on the input and put it onto the wiki:
> https://wiki.apache.org/HttpComponents/GitGuidelines
>
> Here is verbatim copy:
> = Typical Issue Workflow =
>
> 1. Branch off master ({{{git checkout -b / m
[
https://issues.apache.org/jira/browse/HTTPCORE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010998#comment-16010998
]
Gary Gregory commented on HTTPCORE-466:
---
OK, I will do it.
> Round out the SslCon
[
https://issues.apache.org/jira/browse/HTTPCORE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011012#comment-16011012
]
Gary Gregory commented on HTTPCORE-466:
---
{noformat}
commit ccbccceda974f828bfd7d3e
[
https://issues.apache.org/jira/browse/HTTPCORE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011014#comment-16011014
]
Gary Gregory commented on HTTPCORE-466:
---
Next, I will propose a branch for 5.0.
>
Am 2017-05-15 um 19:35 schrieb Gary Gregory:
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov wrote:
Folks,
I have updated the link based on the input and put it onto the wiki:
https://wiki.apache.org/HttpComponents/GitGuidelines
Here is verbatim copy:
= Typical Issue Workflow =
1. Branch o
On Mon, 2017-05-15 at 18:34 +0200, Michael Osipov wrote:
> Folks,
>
> I have updated the link based on the input and put it onto the wiki:
> https://wiki.apache.org/HttpComponents/GitGuidelines
>
> Here is verbatim copy:
> = Typical Issue Workflow =
>
> 1. Branch off master ({{{git checkout -b
On Mon, May 15, 2017 at 11:13 AM, Michael Osipov
wrote:
> Am 2017-05-15 um 19:35 schrieb Gary Gregory:
>
>> On Mon, May 15, 2017 at 9:34 AM, Michael Osipov
>> wrote:
>>
>> Folks,
>>>
>>> I have updated the link based on the input and put it onto the wiki:
>>> https://wiki.apache.org/HttpComponen
Jordan Zimmerman created HTTPASYNC-122:
--
Summary: CloseableHttpAsyncClient executed old versions of requests
Key: HTTPASYNC-122
URL: https://issues.apache.org/jira/browse/HTTPASYNC-122
Project: Ht
On Mon, 2017-05-15 at 20:13 +0200, Michael Osipov wrote:
> Am 2017-05-15 um 19:35 schrieb Gary Gregory:
> > On Mon, May 15, 2017 at 9:34 AM, Michael Osipov >
> > Which of the paths should we pick:
> > https://makandracards.com/makandra/527-squash-several-git-commits-i
> > nto-a-single-commit
> >
On Mon, 2017-05-15 at 18:06 +, Gary Gregory (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/HTTPCORE-466?page=com.atl
> assian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=16011014#comment-16011014 ]
>
> Gary Gregory commented on HTTPCORE-466:
> -
[
https://issues.apache.org/jira/browse/HTTPASYNC-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011049#comment-16011049
]
Oleg Kalnichevski commented on HTTPASYNC-122:
-
Please attach wire / context
Am 2017-05-15 um 20:18 schrieb Gary Gregory:
On Mon, May 15, 2017 at 11:13 AM, Michael Osipov
wrote:
Am 2017-05-15 um 19:35 schrieb Gary Gregory:
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov
wrote:
Folks,
I have updated the link based on the input and put it onto the wiki:
https://wik
Am 2017-05-15 um 20:22 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 20:13 +0200, Michael Osipov wrote:
Am 2017-05-15 um 19:35 schrieb Gary Gregory:
On Mon, May 15, 2017 at 9:34 AM, Michael Osipov
...
Which of the paths should we pick:
https://makandracards.com/makandra/527-squash-sever
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki"
for change notification.
The "GitGuidelines" page has been changed by MichaelOsipov:
https://wiki.apache.org/HttpComponents/GitGuidelines?action=diff&rev1=5&rev2=6
Comment:
Replaced master with release
Am 2017-05-15 um 20:18 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 18:34 +0200, Michael Osipov wrote:
Folks,
I have updated the link based on the input and put it onto the wiki:
https://wiki.apache.org/HttpComponents/GitGuidelines
Here is verbatim copy:
= Typical Issue Workflow =
1. Br
On Mon, May 15, 2017 at 11:37 AM, Michael Osipov
wrote:
> Am 2017-05-15 um 20:18 schrieb Oleg Kalnichevski:
>
>> On Mon, 2017-05-15 at 18:34 +0200, Michael Osipov wrote:
>>
>>> Folks,
>>>
>>> I have updated the link based on the input and put it onto the wiki:
>>> https://wiki.apache.org/HttpComp
[
https://issues.apache.org/jira/browse/HTTPASYNC-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman updated HTTPASYNC-122:
---
Attachment: log.txt
Here's the log when the problem exhibited. Let me know if this
Am 2017-05-15 um 20:43 schrieb Gary Gregory:
On Mon, May 15, 2017 at 11:37 AM, Michael Osipov
wrote:
Am 2017-05-15 um 20:18 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 18:34 +0200, Michael Osipov wrote:
Folks,
I have updated the link based on the input and put it onto the wiki:
https
On Mon, May 15, 2017 at 11:57 AM, Michael Osipov
wrote:
> Am 2017-05-15 um 20:43 schrieb Gary Gregory:
>
>> On Mon, May 15, 2017 at 11:37 AM, Michael Osipov
>> wrote:
>>
>> Am 2017-05-15 um 20:18 schrieb Oleg Kalnichevski:
>>>
>>> On Mon, 2017-05-15 at 18:34 +0200, Michael Osipov wrote:
>>>
[
https://issues.apache.org/jira/browse/HTTPASYNC-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman updated HTTPASYNC-122:
---
Attachment: log.txt.zip
Sorry - wire was missing. This is the full log.
> Closeabl
On Mon, May 15, 2017 at 11:59 AM, Gary Gregory
wrote:
> On Mon, May 15, 2017 at 11:57 AM, Michael Osipov
> wrote:
>
>> Am 2017-05-15 um 20:43 schrieb Gary Gregory:
>>
>>> On Mon, May 15, 2017 at 11:37 AM, Michael Osipov
>>> wrote:
>>>
>>> Am 2017-05-15 um 20:18 schrieb Oleg Kalnichevski:
>
Hi,
I find it inconvenient that:
org.apache.http.nio.protocol.HttpAsyncService.requestReceived(NHttpServerConnection)
Does not take an HttpContext argument.
I'm not sure there is pretty way to fix this in 4.4.x with BC.
I'm not looked at 5.0.x yet.
Gary
--
E-Mail: garydgreg...@gmail.com | g
[
https://issues.apache.org/jira/browse/HTTPASYNC-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman resolved HTTPASYNC-122.
Resolution: Not A Problem
OK - this was my error. My code was in a loop sending 1
Gary Gregory created HTTPCORE-467:
-
Summary: Add getter methods to HttpAsyncService for subclasses to
access instance variables
Key: HTTPCORE-467
URL: https://issues.apache.org/jira/browse/HTTPCORE-467
In order to my HttpAsyncService to be coded cleanly, I would like to add
getter methods to HttpAsyncService for subclasses to access instance
variables:
https://issues.apache.org/jira/browse/HTTPCORE-467
Any objections?
Gary
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persiste
[
https://issues.apache.org/jira/browse/HTTPCORE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated HTTPCORE-467:
--
Description:
Add getter methods to {{org.apache.http.nio.protocol.HttpAsyncService}} for
subc
[
https://issues.apache.org/jira/browse/HTTPCORE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated HTTPCORE-467:
--
Description:
In order to my {{org.apache.http.nio.protocol.HttpAsyncService}} subclass to be
Gary Gregory created HTTPCORE-468:
-
Summary: Allow HttpAsyncService subclasses to customize the HTTP
status code
Key: HTTPCORE-468
URL: https://issues.apache.org/jira/browse/HTTPCORE-468
Project: Http
61 matches
Mail list logo
