Am 2022-11-14 um 23:05 schrieb Gary D. Gregory:
Hi Oleg and All:
Our commits mailing list reports that some commits I pushed today to
httpcomponents-core were erased from history.
Is this an innocent mistake in your use of git?
See below for the email. Specifically the commits I do not see bu
I would expect master to be protected and be solely linear. To avoid
accidential force pushes. Only in extreme cases a rebase should be
necessary on master.
Only release tags are protected. Master is just an ordinary development
branch. If you do not like the name confusion, it can be r
We have an implicit commit-them-review policy ever since the inception
of the project in the year of 2005. We all are free to commit what we
deem appropriate but no commit can be considered safe until it has been
voted upon and tagged with a release tag.
If an objection has been raised about a
[
https://issues.apache.org/jira/browse/HTTPCLIENT-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634371#comment-17634371
]
Sam Brannen commented on HTTPCLIENT-2227:
-
Thanks for reporting it to INFRA.
[
https://issues.apache.org/jira/browse/HTTPCLIENT-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Brannen closed HTTPCLIENT-2227.
---
Resolution: Fixed
> HttpClient API docs are not reachable
>
Am 2022-11-15 um 14:32 schrieb Oleg Kalnichevski:
We have an implicit commit-them-review policy ever since the inception
of the project in the year of 2005. We all are free to commit what we
deem appropriate but no commit can be considered safe until it has been
voted upon and tagged with a rel
This is a distraction from the problem I brought up in another thread: Oleg
erases other people's commits at he wishes, CTR or RTC won't matter. This
is not the Apache way.
Gary
On Tue, Nov 15, 2022, 15:37 Michael Osipov wrote:
> Am 2022-11-15 um 14:32 schrieb Oleg Kalnichevski:
> > We have an
Oleg,
can you explain why previous versions of the autogenerated website point
to the newest one? Consider someone is consuming the Javadoc from his
IDE. I guess the user will be redirected in the IDE and will see *not*
the Javadoc for the version he has configured, no?
Michael
Thanks for bringing this up!
I prefer RTC myself for a number of reasons:
It's easier for me to follow development when I get PR notifications, the
github PR UI is fantastic.
Based on email updates from PR discussion, I can join conversations where I
have relevant experience.
Even for minor chan
On Tue, Nov 15, 2022, at 15:41, Gary Gregory wrote:
> This is a distraction from the problem I brought up in another thread: Oleg
> erases other people's commits at he wishes, CTR or RTC won't matter. This
> is not the Apache way.
Was this omission intentional, or accidental?
On Tue, 2022-11-15 at 15:41 -0500, Gary Gregory wrote:
> This is a distraction from the problem I brought up in another
> thread: Oleg
> erases other people's commits at he wishes, CTR or RTC won't matter.
> This
> is not the Apache way.
>
You have a long history of making really bad changes to t
On Tue, 2022-11-15 at 21:58 +0100, Michael Osipov wrote:
> Oleg,
>
> can you explain why previous versions of the autogenerated website
> point
> to the newest one? Consider someone is consuming the Javadoc from his
> IDE. I guess the user will be redirected in the IDE and will see
> *not*
> the
12 matches
Mail list logo
