Thanks David.
On Thu, Mar 27, 2025 at 9:50 AM David Arthur wrote:
> Commented-by: left any comment on the PR (any contributor)
> Reviewed-by: did a full review on the PR (any contributor)
> Approved-by: committer(s) who approved the PR
This matches my understanding and captures contributors' int
; participated in the discussion versus contributors (committers and
> non-committers) that actually agree with the change and think that
> should be included in Apache Kafka.
>
> Thanks,
> -Jose
>
> On Tue, Mar 25, 2025 at 8:06 PM David Arthur wrote:
> >
> > Hel
I see two problems that this solves.
1) Gets the history of approver out of GitHub and into our log (no need to
look back at the PR)
2) Gives proper attribution for the single person responsible for
committing/approving the code (untangle all the "Reviewers:")
And yea, I think it can be totally a
What's the burden if it's automated? I agree we should keep it simple for
anything that has to be done manually.
Ismael
On Tue, Apr 1, 2025 at 5:45 PM Matthias J. Sax wrote:
> Hi,
>
> I understand the problem of a long "Reviewers" line and line break, so
> breaking it down into multiple lines,
Hi,
I understand the problem of a long "Reviewers" line and line break, so
breaking it down into multiple lines, one per reviewer make sense to me.
I don't see much value in using all these other trailers personally, and
all the question about "when to add whom to which trailer" kinda backs
hi David
> David Arthur 於 2025年3月27日 晚上9:50 寫道：
>
> Commented-by: left any comment on the PR (any contributor)
> Reviewed-by: did a full review on the PR (any contributor)
> Approved-by: committer(s) who approved the PR
If a committer leaves the comment without approve, he/she should be include
required trailer. Since
> > approving
> > > a PR implies a review, I think we can keep the mandatory trailers just
> > to a
> > > single one.
> > >
> > > "Co-authored-by" is added automatically by GitHub if a PR has commits
> > from
> &
andatory trailers just
> to a
> > single one.
> >
> > "Co-authored-by" is added automatically by GitHub if a PR has commits
> from
> > another author. I don't think we can modify this.
> >
> > "Signed-off-by" is added automatically by Git
lies a review, I think we can keep the mandatory trailers just to a
> single one.
>
> "Co-authored-by" is added automatically by GitHub if a PR has commits from
> another author. I don't think we can modify this.
>
> "Signed-off-by" is added automatical
PR has commits from
another author. I don't think we can modify this.
"Signed-off-by" is added automatically by GitHub if a PR has commits which
were cryptographically signed (e.g. "git commit -S"). Again, we can't
control this.
For the two trailers automatically added
t usage. Is the equivalent of the
"Signed-off-by" header already captured by git/GitHub on merge?
Thanks,
Kirk
On Tue, Mar 25, 2025, at 5:06 PM, David Arthur wrote:
> Hello Kafka community!
>
> I wanted to start a discussion around our Git commits and the metadata we
> keep in
pache Kafka.
Thanks,
-Jose
On Tue, Mar 25, 2025 at 8:06 PM David Arthur wrote:
>
> Hello Kafka community!
>
> I wanted to start a discussion around our Git commits and the metadata we
> keep in them.
>
> We have historically used the "Reviewers" Git trailer [1] to
stent Git
trailer style (separate line per individual for all of them since that's
what GitHub expects for "Co-authored-by").
Additional comments:
1. Having tooling that automatically extracts the approvals and people who
commented from the PR would be super helpful.
2. What'
Hello Kafka community!
I wanted to start a discussion around our Git commits and the metadata we
keep in them.
We have historically used the "Reviewers" Git trailer [1] to indicate who
had reviewed a commit. Originally, it seems we used this field to indicate
the committer who ap
Lianet Magrans created KAFKA-18973:
--
Summary: Review
MetadataSchemaCheckerToolTest.testVerifyEvolutionGit requiring git project
Key: KAFKA-18973
URL: https://issues.apache.org/jira/browse/KAFKA-18973
Greg Harris created KAFKA-18460:
---
Summary: MetadataSchemaCheckerTool verify-evolution-git is broken
in Git worktrees
Key: KAFKA-18460
URL: https://issues.apache.org/jira/browse/KAFKA-18460
Project
fic git hash
>
>
> Key: KAFKA-17193
> URL: https://issues.apache.org/jira/browse/KAFKA-17193
> Project: Kafka
> Issue Type: Task
>Reporter: Mickael Maison
>
Mickael Maison created KAFKA-17193:
--
Summary: Pin external GitHub actions to specific git hash
Key: KAFKA-17193
URL: https://issues.apache.org/jira/browse/KAFKA-17193
Project: Kafka
Issue
mumrah merged PR #24:
URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/24
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr
mumrah opened a new pull request, #24:
URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/24
This will let us verify the merge group behavior.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
Greg,
Thanks for making the change and sharing the benefit with the overall group.
Ismael
On Mon, Oct 23, 2023 at 10:03 AM Greg Harris
wrote:
> Hey Kafka Developers,
>
> This is a small announcement that the gradle build now supports the
> git-worktree subcommand [1] on the 3.4, 3
Hey Kafka Developers,
This is a small announcement that the gradle build now supports the
git-worktree subcommand [1] on the 3.4, 3.5, 3.6, and trunk branches
[2].
If you've needed to check out multiple copies of Kafka concurrently,
you previously needed to manage multiple full clones o
Divij Vaidya created KAFKA-15201:
Summary: When git fails, script goes into a loop
Key: KAFKA-15201
URL: https://issues.apache.org/jira/browse/KAFKA-15201
Project: Kafka
Issue Type: Sub-task
Greg Harris created KAFKA-14767:
---
Summary: Gradle build fails with missing commitId after git gc
Key: KAFKA-14767
URL: https://issues.apache.org/jira/browse/KAFKA-14767
Project: Kafka
Issue
Venom-git opened a new pull request #395:
URL: https://github.com/apache/kafka-site/pull/395
Please help to update our organization as well , as we are using #Apache
Kafka in our environment.
Ismael
On Fri, Dec 7, 2018, 9:31 AM Daniel Gruno On 12/7/18 6:28 PM, Ismael Juma wrote:
> > Hi Daniel,
> >
> > We moved to Gitbox a while back for kafka and kafka-site. Which
> > repository is still usi
On Fri, Dec 7, 2018 at 12:29 PM Ismael Juma wrote:
>
> Hi Daniel,
>
> We moved to Gitbox a while back for kafka and kafka-site. Which repository is
> still using git-wip-us.apache.org?
>
> Ismael
None of yours. The message was sent to every PMC.
I believe https://git1-us-
On 12/7/18 6:28 PM, Ismael Juma wrote:
Hi Daniel,
We moved to Gitbox a while back for kafka and kafka-site. Which
repository is still using git-wip-us.apache.org
<http://git-wip-us.apache.org>?
Ismael
Hi Ismael,
You do not have any repositories that need to be moved, Kafka can
Hi Daniel,
We moved to Gitbox a while back for kafka and kafka-site. Which repository
is still using git-wip-us.apache.org?
Ismael
On Fri, Dec 7, 2018 at 8:53 AM Daniel Gruno wrote:
> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
> DISREGARD THIS EMAIL; IT WA
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
Hello Apache projects,
I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
That was it, thanks! But I still don't understand how I had tags for 1.0.0,
but not 0.11.0.0.
On 10 November 2017 at 13:10, Kamal wrote:
> Try, `git fetch upstream --tags`
>
> On Fri, Nov 10, 2017 at 6:32 PM, Mickael Maison
> wrote:
>
> > Have you tried:
> > g
Try, `git fetch upstream --tags`
On Fri, Nov 10, 2017 at 6:32 PM, Mickael Maison
wrote:
> Have you tried:
> git fetch --tags ?
>
> On Fri, Nov 10, 2017 at 12:54 PM, Tom Bentley
> wrote:
> > Not when I run `git tag` locally though.
> >
> > On 10 November
Have you tried:
git fetch --tags ?
On Fri, Nov 10, 2017 at 12:54 PM, Tom Bentley wrote:
> Not when I run `git tag` locally though.
>
> On 10 November 2017 at 12:44, Ismael Juma wrote:
>
>> They seem to be there:
>>
>> https://github.com/apache/kafka/tree/0.11.0.
Not when I run `git tag` locally though.
On 10 November 2017 at 12:44, Ismael Juma wrote:
> They seem to be there:
>
> https://github.com/apache/kafka/tree/0.11.0.0
> https://github.com/apache/kafka/tree/0.11.0.1
>
> Ismael
>
> On Fri, Nov 10, 2017 at 12:41 PM, Tom B
They seem to be there:
https://github.com/apache/kafka/tree/0.11.0.0
https://github.com/apache/kafka/tree/0.11.0.1
Ismael
On Fri, Nov 10, 2017 at 12:41 PM, Tom Bentley wrote:
> I just noticed that although every other release is tagged in git there are
> no tags for 0.11.0.0 and 0.11.0.
I just noticed that although every other release is tagged in git there are
no tags for 0.11.0.0 and 0.11.0.1. Did something go wrong? Please can they
be tagged retrospectively?
Cheers,
Tom
d as they are no longer active. We've recently started to follow a bit
more strict policy re: tagging RCs and releases; we might want to also come up
with a policy for retiring & tagging the final version of branches.
> Delete old unused bran
Jeff Widman created KAFKA-4519:
--
Summary: Delete old unused branches in git repo
Key: KAFKA-4519
URL: https://issues.apache.org/jira/browse/KAFKA-4519
Project: Kafka
Issue Type: Task
Github user guozhangwang closed the pull request at:
https://github.com/apache/kafka/pull/1922
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature i
GitHub user guozhangwang opened a pull request:
https://github.com/apache/kafka/pull/1922
HOTFIX: remove git conflicts
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/guozhangwang/kafka KHotfix-streams-html
Alternatively you
Github user SinghAsDev closed the pull request at:
https://github.com/apache/kafka/pull/1274
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user SinghAsDev opened a pull request:
https://github.com/apache/kafka/pull/1274
Git ignore idea's specific /out/ and .DS_Store.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SinghAsDev/kafka MinorGiti
uest at:
https://github.com/apache/kafka/pull/485
> Release artifact expects a git repository for the release audit tool (RAT)
> --
>
> Key: KAFKA-2797
> URL: https://iss
485
[https://github.com/apache/kafka/pull/485]
> Release artifact expects a git repository for the release audit tool (RAT)
> --
>
> Key: KAFKA-2797
> URL: https://issues.apache.
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/485
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
[
https://issues.apache.org/jira/browse/KAFKA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava reassigned KAFKA-2797:
Assignee: Ewen Cheslack-Postava
> Release artifact expects a
ase artifact expects a git repository for the release audit tool (RAT)
> --
>
> Key: KAFKA-2797
> URL: https://issues.apache.org/jira/browse/KAFKA-2797
> Project: Kafka
>
uest:
https://github.com/apache/kafka/pull/485
KAFKA-2797: Only run rat when in the .git repository since it require s the
.gitignore to generate the list of files to ignore
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/k
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/485
KAFKA-2797: Only run rat when in the .git repository since it require s the
.gitignore to generate the list of files to ignore
You can merge this pull request into a Git repository by running
Flavio Junqueira created KAFKA-2797:
---
Summary: Release artifact expects a git repository for the release
audit tool (RAT)
Key: KAFKA-2797
URL: https://issues.apache.org/jira/browse/KAFKA-2797
[
https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Junqueira resolved KAFKA-2612.
-
Resolution: Fixed
> Increase the number of retained builds for kafka-trunk-git-pr-j
7 PM:
--
(I said 15 previously but set to 14, so I'm just correcting the value with this
edit)
OK, to play nicely, I've set for the git-pr job the number of days to keep to
14 and max number of builds to 100. It sounds better to set a threshold, even
if large.
was (Author
etained builds for kafka-trunk-git-pr-jdk7
> --
>
> Key: KAFKA-2612
> URL: https://issues.apache.org/jira/browse/KAFKA-2612
> Project: Kafka
> Issue Type: Improvement
>
t for the git-pr job the number of days to keep to
15 and max number of builds to 100. It sounds better to set a threshold, even
if large.
> Increase the number of retained builds for kafka-trunk-git-pr-jdk7
> --
>
>
unk-git-pr-jdk7
> --
>
> Key: KAFKA-2612
> URL: https://issues.apache.org/jira/browse/KAFKA-2612
> Project: Kafka
> Issue Type: Improvement
>
Comments below.
On Tue, Oct 6, 2015 at 1:39 PM, Manikumar Reddy
wrote:
> On Tue, Oct 6, 2015 at 1:34 PM, Ismael Juma wrote:
>
> > Thanks Mani. Regarding the release process changes, a couple of comments:
> >
> > 1. Under "bug-fix releases", you mention "major release directory" a
> couple
> > o
ase the number of retained builds for kafka-trunk-git-pr-jdk7
> --
>
> Key: KAFKA-2612
> URL: https://issues.apache.org/jira/browse/KAFKA-2612
> Project: Kafka
>
t;Days to keep builds" rather than "Max # of builds
to keep". I think we should switch to number of days, something like 21 days,
sounds good? [~ijuma]
> Increase the number of retained builds
mand used to do this as well?
>
Yes, updated the wiki page.
>
> Ismael
>
> On Tue, Oct 6, 2015 at 3:37 AM, Manikumar Reddy
> wrote:
>
> > Hi Gwen,
> >
> > Kafka site is updated to use Git repo. We can now push any site changes
> to
> > git web site rep
[
https://issues.apache.org/jira/browse/KAFKA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-2612:
---
Component/s: build
> Increase the number of retained builds for kafka-trunk-git-pr-j
help?
> Increase the number of retained builds for kafka-trunk-git-pr-jdk7
> --
>
> Key: KAFKA-2612
> URL: https://issues.apache.org/jira/browse/KAFKA-2612
> Project: Kafka
Ismael Juma created KAFKA-2612:
--
Summary: Increase the number of retained builds for
kafka-trunk-git-pr-jdk7
Key: KAFKA-2612
URL: https://issues.apache.org/jira/browse/KAFKA-2612
Project: Kafka
including the command used to do this as well?
Ismael
On Tue, Oct 6, 2015 at 3:37 AM, Manikumar Reddy
wrote:
> Hi Gwen,
>
> Kafka site is updated to use Git repo. We can now push any site changes to
> git web site repo.
>
> 1) "Contributing website changes" wiki p
Hi Gwen,
Kafka site is updated to use Git repo. We can now push any site changes to
git web site repo.
1) "Contributing website changes" wiki page:
https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Website+Documentation+Changes
2) "Website update process" adde
On 3 Oct 2015 16:44, "Gwen Shapira" wrote:
> OK, PR 171 is in, and the latest version of the docs is now in docs/
> directory of trunk!
Awesome. :)
> Next steps:
> 1. Follow up with infra on our github site
Follow-up issue filed:
https://issues.apache.org/jira/browse/INFRA-10539. Geoffrey
Core
M, Manikumar Reddy
> wrote:
>
> > Thanks Gwen, i will
> > update the next steps.
> > On Oct 3, 2015 1:08 AM, "Gwen Shapira" wrote:
> >
> > > Hi,
> > >
> > > I created asf-git under
> > https://git-wip-us.apache.org/repos/asf/k
on those?
Anything I'm missing?
Gwen
On Fri, Oct 2, 2015 at 11:28 PM, Manikumar Reddy
wrote:
> Thanks Gwen, i will
> update the next steps.
> On Oct 3, 2015 1:08 AM, "Gwen Shapira" wrote:
>
> > Hi,
> >
> > I created asf-git under
> ht
://github.com/apache/kafka/pull/171]
> Migrate website from SVN to Git
>
>
> Key: KAFKA-2425
> URL: https://issues.apache.org/jira/browse/KAFKA-2425
> Project: Kafka
> Issue Type: Improvement
uest at:
https://github.com/apache/kafka/pull/171
> Migrate website from SVN to Git
>
>
> Key: KAFKA-2425
> URL: https://issues.apache.org/jira/browse/KAFKA-2425
> Project: Kafka
>
Thanks Gwen, i will
update the next steps.
On Oct 3, 2015 1:08 AM, "Gwen Shapira" wrote:
> Hi,
>
> I created asf-git under https://git-wip-us.apache.org/repos/asf/kafka-site
> .
> git and pushed our existing docs in there.
> What do we need to do to get infra
ibute changes to the relevant branch of the code
repository and this will be pushed to the website Git repo as needed.
Does Infra supports git based sites?
>
Yes.
Ismael
Thanks Gwen. Comments below.
On Fri, Oct 2, 2015 at 8:38 PM, Gwen Shapira wrote:
> I created asf-git under https://git-wip-us.apache.org/repos/asf/kafka-site
> .
> git and pushed our existing docs in there.
> What do we need to do to get infra to show this in our website?
>
You
On Fri, Oct 2, 2015 at 12:38 PM, Gwen Shapira wrote:
> Hi,
>
> I created asf-git under https://git-wip-us.apache.org/repos/asf/kafka-site.
> git and pushed our existing docs in there.
> What do we need to do to get infra to show this in our website?
>
> Next steps:
> 1)
Hi,
I created asf-git under https://git-wip-us.apache.org/repos/asf/kafka-site.
git and pushed our existing docs in there.
What do we need to do to get infra to show this in our website?
Next steps:
1) Minor fix to PR 171
2) Merge PR 171
3) Get Apache to show our git site
4) Update wiki with
Hi Gwen,
We need to create new branch named "asf-site" in new git repository[1].
This is requirement from Apache Infra
for git based websites [2]. After creating new branch, we will the copy
the existing to svn repo contents to
new branch.
1. https://git-wip-us.apache.org/repos
> Jun/Gwen/Guozhang,
>Need your help to complete this.
>
> (1) Copy latest docs to kafka repo:
> https://github.com/apache/kafka/pull/171
>
> (2) svn site repo -> git site repo migration : need committer help to
> create a branch "asf-site".
>
>
Jun/Gwen/Guozhang,
Need your help to complete this.
(1) Copy latest docs to kafka repo:
https://github.com/apache/kafka/pull/171
(2) svn site repo -> git site repo migration : need committer help to
create a branch "asf-site".
new git site repo :
https://git-wip-
Some questions: This PR contains generated javadocs also. Do we need to
copy javadocs here?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/omkreddy/kafka
KAFKA-2425-MOVE-DOCS-TO-KAFKA-REPO
Alternatively you can review and apply these changes as
pull request at:
https://github.com/apache/kafka/pull/171
> Migrate website from SVN to Git
>
>
> Key: KAFKA-2425
> URL: https://issues.apache.org/jira/browse/KAFKA-2425
> Project: Kafka
>
Some questions: This PR contains generated javadocs also. Do we need to
copy javadocs here?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/omkreddy/kafka
KAFKA-2425-MOVE-DOCS-TO-KAFKA-REPO
Alternatively you can review and apply these changes as
nd migrate the existing
> svn site repo to new git repo.
>
> (1) Gwen's suggestion will help to us maintain latest docs in Kafka repo
> itself. We periodically need to copy these latest docs to site repo. I
> will submit patch for this.
>
> (2) svn repo -> git rep
Hi Guozhang,
Our plan is to follow Gwen's suggested approach and migrate the existing
svn site repo to new git repo.
(1) Gwen's suggestion will help to us maintain latest docs in Kafka repo
itself. We periodically need to copy these latest docs to site repo. I
will submit patc
I thought Gwen's suggestion was to us a separate folder in the same repo
for docs instead of a separate branch, Gwen can correct me if I was wrong?
Guozhang
On Mon, Aug 24, 2015 at 10:31 AM, Manikumar Reddy
wrote:
> Hi,
>
>Infra team created git repo for kafka site doc
Hi,
Infra team created git repo for kafka site docs.
Gwen/Guozhang,
Need your help to create a branch "asf-site" and copy the exiting
svn contents to that branch.
git repo: https://git-wip-us.apache.org/repos/asf/kafka-site.git
https://issues.apache.org/jira/browse/I
wrote:
> Hi All,
>
> Can we finalize the approach? So that we can proceed further.
>
> 1. Gwen's suggestion + existing svn repo
> 2. Gwen's suggestion + new git repo for docs
>
> kumar
>
> On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy
> wrote:
>
Hi All,
Can we finalize the approach? So that we can proceed further.
1. Gwen's suggestion + existing svn repo
2. Gwen's suggestion + new git repo for docs
kumar
On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy
wrote:
> Also can we migrate svn repo to git repo? This will h
Also can we migrate svn repo to git repo? This will help us to fix
occasional doc changes/bug fixes through github PR.
On Thu, Aug 20, 2015 at 4:04 AM, Guozhang Wang wrote:
> Gwen: I remembered it wrong. We would not need another round of voting.
>
> On Wed, Aug 19, 2015 at 3:06
ang Wang wrote:
>
> > So I think we have two different approaches here. The original proposal
> > from Aseem is to move website from SVN to a separate Git repo, and hence
> > have separate commits on code / doc changes. For that we have accumulated
> > enough binging +
Looking back at this thread, the +1 mention "same repo", so I'm not sure a
new vote is required.
On Wed, Aug 19, 2015 at 3:00 PM, Guozhang Wang wrote:
> So I think we have two different approaches here. The original proposal
> from Aseem is to move website from SVN to a s
So I think we have two different approaches here. The original proposal
from Aseem is to move website from SVN to a separate Git repo, and hence
have separate commits on code / doc changes. For that we have accumulated
enough binging +1s to move on; Gwen's proposal is to move website into the
+1 to what Gwen has suggested. This is what we follow in Flume.
All the latest doc changes are in git, once ready you move changes to
svn to update website.
The only catch is, when you need to update specific changes to website
outside release cycle, need to be a bit careful :)
On Wed, Aug 19
to cherry pick from
trunk/master to this branch? Then the commits can be done to master and let the
script do the cherry picks. Don't know how to do it but will look if it is
possible.
> Migrate website from SVN to Git
>
>
>
Then the commits can be done to master and let the
script do the cherry picks. Don't know how to do it but will look if it is
possible.
> Migrate website from SVN to Git
>
>
> Key: KAFKA-2425
> URL: https:
9, 2015 at 8:56 AM, Manikumar Reddy
> wrote:
>
> > oops.. i did not check Ismail's mail.
> >
> > On Wed, Aug 19, 2015 at 9:25 PM, Manikumar Reddy
> > wrote:
> >
> > > Hi,
> > >
> > > We have raised a Apache Infra ticket for mi
> >> > > On Thu, Aug 6, 2015 at 1:52 PM, Grant Henke <
> ghe...@cloudera.com>
> >>> >> wrote:
> >>> >> > >
> >>> >> > > > +1 for the same repo. The closer docs can be to code the more
> >>> >> accurate
> >&
; wrote:
>
> > Hi,
> >
> > We have raised a Apache Infra ticket for migrating site docs from svn
> > -> git .
> > Currently, the gitwcsub client only supports using the "asf-site"
> > branch for site docs.
> > Infra team is suggesting to cre
1 - 100 of 221 matches
Mail list logo
