I accidentally committed several large files under
src/test/resources/mojos/detach-distributions/target.
I'm trying to revert the commit, but it seems to have stalled part way
through the 'Writing objects' phase: 54% [27/50]
Please don't make any further commits until 5857b05 has been reverted!
Cannot push the reverted commit, so have raised an INFRA Jira:
https://issues.apache.org/jira/browse/INFRA-26443
On Sun, 19 Jan 2025 at 00:14, sebb wrote:
>
> I misread the git log:
>
> in fact I had accidentally deleted the target directory, thinking it
> was test output.
>
> So the files need
I misread the git log:
in fact I had accidentally deleted the target directory, thinking it
was test output.
So the files need to be restored somehow.
Sebb
On Sat, 18 Jan 2025 at 23:57, sebb wrote:
>
> I accidentally committed several large files under
> src/test/resources/mojos/detach-distribu
Turns out I needed to use the following magic incantation:
$ git config --global http.postBuffer 157286400
So all now restored.
On Sun, 19 Jan 2025 at 00:43, sebb wrote:
>
> Cannot push the reverted commit, so have raised an INFRA Jira:
>
> https://issues.apache.org/jira/browse/INFRA-26443
>
>
On Sat, 18 Jan 2025 at 17:18, Gilles Sadowski wrote:
>
> Le sam. 18 janv. 2025 à 17:22, Gary Gregory a écrit :
> >
> > On Sat, Jan 18, 2025 at 11:05 AM sebb wrote:
> > >
> > > On Sat, 18 Jan 2025 at 15:03, Gilles Sadowski
> > > wrote:
> > > >
> > > > > > TL;DR; Quite some time ago, INFRA offer
thank1
On Sat, 18 Jan 2025 at 02:50, Gary Gregory wrote:
>
> On Fri, Jan 17, 2025 at 4:00 PM sebb wrote:
> >
> > On Fri, 17 Jan 2025 at 17:33, Gary Gregory wrote:
> > >
> > > On Fri, Jan 17, 2025 at 12:14 PM sebb wrote:
> > > >
> > > > On Tue, 7 Jan 2025 at 13:48, Gary Gregory wrote:
> > > >
Has it been released? I cannot find an ANNOUNCE email.
It looks as though updating to this version may require significant
changes to files used to build the site; it would be helpful to
document these in the announce email and RN.
On Tue, 7 Jan 2025 at 20:01, Gary Gregory wrote:
>
> This lazy v
On Sat, 18 Jan 2025 at 14:27, Gilles Sadowski wrote:
>
> Hi.
>
> Le sam. 18 janv. 2025 à 14:46, sebb a écrit :
> >
> > Several Git repos have files with CRLF line endings even when checked
> > out on Unix or macOS.
> >
> > This can cause problems when editing, and can cause large commit diff
> >
On Sat, 18 Jan 2025 at 15:35, sebb wrote:
>
> On Sat, 18 Jan 2025 at 14:31, Gary Gregory wrote:
> >
> > Git has a setting for that called core.autocrlf and it seems we need to
> > tell people exactly how to use it and put that in our Readme files and
> > source web pages. We should explain how to
Hi sebb,
On 18.01.2025 16:46, sebb wrote:
On Sat, 18 Jan 2025 at 15:35, sebb wrote:
Ideally we need something that is part of the repo checkout.
Has anyone experience of using .gitattributes?
That looks as though it might be a solution.
We are using `.gitattributes` in all Log4j repos with
On Sat, 18 Jan 2025 at 14:31, Gary Gregory wrote:
>
> Git has a setting for that called core.autocrlf and it seems we need to
> tell people exactly how to use it and put that in our Readme files and
> source web pages. We should explain how to use it on macOS, Windows, Linux.
The problem is that
Le sam. 18 janv. 2025 à 17:22, Gary Gregory a écrit :
>
> On Sat, Jan 18, 2025 at 11:05 AM sebb wrote:
> >
> > On Sat, 18 Jan 2025 at 15:03, Gilles Sadowski wrote:
> > >
> > > > > TL;DR; Quite some time ago, INFRA offered the possibility to move
> > > > > the website(s) under "git" control. Is
There are quite a few files in release-plugin with executable permission.
This seems odd, but then I found this commit:
https://lists.apache.org/thread/50bg88ocswo56189vdz5tm2s570szv4y
There is no explanation as to why this is needed.
Any clues?
Other repos also have executable files too.
Seb
On Sat, Jan 18, 2025 at 9:20 AM Gilles Sadowski wrote:
>
> Hi.
>
> Le sam. 18 janv. 2025 à 14:50, Gary Gregory a écrit :
> >
> > On Sat, Jan 18, 2025 at 8:47 AM Gary Gregory wrote:
> > >
> > > On Sat, Jan 18, 2025 at 7:57 AM sebb wrote:
> > > >
> > > > Has it been released? I cannot find an ANN
Le sam. 18 janv. 2025 à 15:37, Gary Gregory a écrit :
>
> On Sat, Jan 18, 2025 at 9:20 AM Gilles Sadowski wrote:
> >
> > Hi.
> >
> > Le sam. 18 janv. 2025 à 14:50, Gary Gregory a
> > écrit :
> > >
> > > On Sat, Jan 18, 2025 at 8:47 AM Gary Gregory
> > > wrote:
> > > >
> > > > On Sat, Jan 18,
On Sat, 18 Jan 2025 at 15:03, Gilles Sadowski wrote:
>
> > > TL;DR; Quite some time ago, INFRA offered the possibility to move
> > > the website(s) under "git" control. Is this related?
> > > If not, and there is a big change, should we reconsider the move?
> >
> > This is not related AFAICT.
> >
We already use .gitattributes in for example:
commons-codec/.gitattributes
commons-geometry/.gitattributes
commons-lang/.gitattributes
commons-logging/.gitattributes
commons-math/.gitattributes
commons-numbers/.gitattributes
commons-parent/.gitattributes
commons-rng/.gitattributes
commons-statisti
Hi Piotr,
Do you need this in each active branch? Does it work with PRs?
TY for the tip!
Gary
On Sat, Jan 18, 2025, 11:25 Piotr P. Karwasz
wrote:
> Hi sebb,
>
> On 18.01.2025 16:46, sebb wrote:
> > On Sat, 18 Jan 2025 at 15:35, sebb wrote:
> >> Ideally we need something that is part of the re
Le sam. 18 janv. 2025 à 17:05, sebb a écrit :
>
> On Sat, 18 Jan 2025 at 15:03, Gilles Sadowski wrote:
> >
> > > > TL;DR; Quite some time ago, INFRA offered the possibility to move
> > > > the website(s) under "git" control. Is this related?
> > > > If not, and there is a big change, should we r
On Sat, Jan 18, 2025 at 8:47 AM Gary Gregory wrote:
>
> On Sat, Jan 18, 2025 at 7:57 AM sebb wrote:
> >
> > Has it been released? I cannot find an ANNOUNCE email.
>
> It looks like I forgot, sending ASAP...
>
> >
> > It looks as though updating to this version may require significant
> > changes
Hi.
Le sam. 18 janv. 2025 à 14:40, sebb a écrit :
>
> There are quite a few files in release-plugin with executable permission.
>
> This seems odd, but then I found this commit:
>
> https://lists.apache.org/thread/50bg88ocswo56189vdz5tm2s570szv4y
>
> There is no explanation as to why this is need
Hi.
Le sam. 18 janv. 2025 à 14:50, Gary Gregory a écrit :
>
> On Sat, Jan 18, 2025 at 8:47 AM Gary Gregory wrote:
> >
> > On Sat, Jan 18, 2025 at 7:57 AM sebb wrote:
> > >
> > > Has it been released? I cannot find an ANNOUNCE email.
> >
> > It looks like I forgot, sending ASAP...
> >
> > >
> >
On Sat, Jan 18, 2025 at 7:57 AM sebb wrote:
>
> Has it been released? I cannot find an ANNOUNCE email.
It looks like I forgot, sending ASAP...
>
> It looks as though updating to this version may require significant
> changes to files used to build the site; it would be helpful to
> document thes
Several Git repos have files with CRLF line endings even when checked
out on Unix or macOS.
This can cause problems when editing, and can cause large commit diff
emails which obscure the actual change.
I'm thinking it might be useful to add a Checkstyle rule to detect such files.
And/or maybe th
Hi.
Le sam. 18 janv. 2025 à 14:46, sebb a écrit :
>
> Several Git repos have files with CRLF line endings even when checked
> out on Unix or macOS.
>
> This can cause problems when editing, and can cause large commit diff
> emails which obscure the actual change.
>
> I'm thinking it might be usef
Git has a setting for that called core.autocrlf and it seems we need to
tell people exactly how to use it and put that in our Readme files and
source web pages. We should explain how to use it on macOS, Windows, Linux.
We probably also need to point out using dos2unix on Windows to clean up
messes
On Sat, Jan 18, 2025 at 11:05 AM sebb wrote:
>
> On Sat, 18 Jan 2025 at 15:03, Gilles Sadowski wrote:
> >
> > > > TL;DR; Quite some time ago, INFRA offered the possibility to move
> > > > the website(s) under "git" control. Is this related?
> > > > If not, and there is a big change, should we re
On Sat, 18 Jan 2025 at 17:07, Alex Herbert wrote:
>
> We already use .gitattributes in for example:
>
> commons-codec/.gitattributes
> commons-geometry/.gitattributes
> commons-lang/.gitattributes
> commons-logging/.gitattributes
> commons-math/.gitattributes
> commons-numbers/.gitattributes
> com
Hi Gary,
On 18.01.2025 18:11, Gary Gregory wrote:
Do you need this in each active branch? Does it work with PRs?
Yes, I am afraid you need it in all the active branches.
It works with PRs, since basically it converts CRLF to LF each time you
call `git add`.
Piotr
Hi Gilles,
On 18.01.2025 18:09, Gilles Sadowski wrote:
Yes, it's likely a lot of work.
Maybe a GSoC project (for which the candidate should somehow
demonstrate the capacity to achieve the result _before_ being
accepted, so that we don't end up doing twice as much work...)?
The changes in `logg
On Sat, 18 Jan 2025 at 18:05, Piotr P. Karwasz
wrote:
> Hi Alex,
>
> On 18.01.2025 18:06, Alex Herbert wrote:
> > $ echo "* text=auto" >>.gitattributes
> > $ rm .git/index # Remove the index to force Git to
> > $ git reset # re-scan the working directory
> > $ git status# Show
Hi Alex,
On 18.01.2025 18:06, Alex Herbert wrote:
$ echo "* text=auto" >>.gitattributes
$ rm .git/index # Remove the index to force Git to
$ git reset # re-scan the working directory
$ git status# Show files that will be normalized
$ git add -u
$ git add .gitattributes
$ git
32 matches
Mail list logo
