Re: [git-users] GIT failed to checkout the linux kernel on a 6 GB system

[skybuck2000]

On Thursday, December 2, 2021 at 11:16:34 AM UTC+1 Konstantin Khomoutov 
wrote:

> On Wed, Dec 01, 2021 at 09:01:36PM -0800, skybuck2000 wrote: 
>
> > I would like to report that GIT failed to checkout the linux kernel on a 
> 6 
> > GB system. 
> > 
> > For now I believe it ran out of memory. I only tried once. 
> > 
> > PAGEFILE.SYS on this system was disabled. 
>
> [...] 
>
 

> * 99% of systems Git runs on do not have the concept of "PAGEFILE.SYS", 
> and 
> you do not even bother to think about this. Please do. 
>

I do not know what pagefile.sys is called on other systems. Now that I have 
run ubunty/linux it seems to be called "swap" or "swap file".

I will assume most users are experienced enough in the field of computers 
to have seen windows in their lifetime at least once and know what a 
pagefile is and the concept behind it so I don't have to call it "swap" or 
whatever the concurrent flavor of term is for os.

Bye for now,
  Skybuck.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/68431f0f-593e-4dc1-8aac-f0434f4e28e2n%40googlegroups.com.

Re: [git-users] GITK: Useability issue, can't scroll through fie list ?

[skybuck2000]

On Thursday, December 2, 2021 at 11:07:39 AM UTC+1 Konstantin Khomoutov 
wrote:

> On Wed, Dec 01, 2021 at 09:55:38PM -0800, skybuck2000 wrote: 
>
> > I see two issues right now: 
>
> [...] 
>
> Please stop reporting bugs on this list. 
>

Perhaps I will, however users may have work arounds or different oppinions 
if it's really a bug or not.
 

> As I've suggested several times before, this list is dedicated to help 
> inexperienced Git users solve the problems they have when using Git. 
>

Do you consider this scroll issue a bug ? It may be a design issue ? It may 
also be that there are options to change it's behaviour.

I am not certain yet that it is a bug, perhaps it's a configuration kind of 
thing.
 

> Discussing usability issues or apparent bugs is just pointless here for 
> the 
> two reasons: 1) this list is not read by Git developers (who could try to 
> fix 
> the code), and 2) no one else is going to report bugs for you.


Again usability might be a question of configuration.

Also if there is consensus of other users that something is annoying and 
the behaviour should be changed might also help convince developers a 
change is a good idea.
 

>
>
> Please re-read . 
>

Thanks this is helpfull, don't think I have seen it before, saved it in my 
bookmarks.

Oh, and while we're at it, one more kind request: please stop posting 
> identical e-mails to both git-users and git-for-windows. Again, as I've 
>

This I can do, however it can be usefull to get different kinds of feedback 
based on user group.

I am not so familiar yet with these groups and I have no idea how many 
readers are in each group.
 

> suggested elsewhere, the former list is for discussing basic _generic_ 
> problems with Git - no matter which flavour it is and on which platform it 
> runs on, - and the latter is for solving problems specific to Windows and 
> Git-for-Windows as the de-facto standard ongoing port of Git to that 
> platform. 
>
>
I am unsure how to identify windows specific git problems.

Bye for now,
  Skybuck.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/03fb2ac7-0c1a-4e2b-85e2-6a417a94b610n%40googlegroups.com.

[git-users] Why is this window annyoingly small on to the bottom right ?

[skybuck2000]

Text windows should always be center, and big... 

Eye strain is a real thing... and this is kinda annoying and feels 
retarded... sorry...

got used to it, but it's inconstant with other newsgroups where the window 
is center and big ?!

Is window setting a google specific thing and if so why ?

Seen it before on other groups possibly.. confusing... 

Bye,
  Skybuck.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/5686d044-05ec-4f19-9c11-4952f3b345bdn%40googlegroups.com.

[git-users] FIGLIO DI GRAN TROIA #PIERSILVIOBERLUSCONI (ANCOR PIÚ, FIGLIO DI PEDOFILO MACELLA MAGISTRATI #SILVIOBERLUSCONI) RICICLA MONTAGNE DI SOLDI MAFIOSI, COME FATTO DA SUO NONNO, MASSONE CRIMINAL

[FRANCESCA DONATO. MASSONERIA ZAGAMIANA DI DESTRA]

FIGLIO DI GRAN TROIA #PIERSILVIOBERLUSCONI (ANCOR PIÚ, FIGLIO DI PEDOFILO 
MACELLA MAGISTRATI #SILVIOBERLUSCONI) RICICLA MONTAGNE DI SOLDI MAFIOSI, 
COME FATTO DA SUO NONNO, MASSONE CRIMINALISSIMO #LUIGIBERLUSCONI, IN 
#BANCARASINI! E COME FATTO PER. MEZZO SECOLO, DAL LECCA FIGHE DI 
BAMBINE ED ADOLESCENTI, BASTARDO STRAGISTA, MANDANTE DI ALMENO 900 OMICIDI 
MASSO^MAFIOSI, NONCHÉ PEDOFILISSIMO SILVIO BERLUSCONI! CASH ASSASSINO, 
DICEVO! ESATTAMENTE DI #COSANOSTRA, #CAMORRA, #NDRANGHETA, 
#SACRACORONAUNITA, SOCIETAFOGGIANA, MAFIA DI SAN SEVERO, MAFIA DI APRICENA, 
MAFIA DI LESINA, MAFIA RUSSA, MAFIA CINESE, MAFIA COLOMBIANA, MAFIA 
MESSICANA, MAFIA MAROCCHINA, MAFIA ALBANESE, MAFIA SLAVA, MAFIA RUMENA! CE 
NE SCRIVE IL MIO BANCHIERE PREFERITO IN SVIZZERA: #ANDREASNIGG DI BANK J 
SAFRA SARASIN ZURIGO! CHE TANTE VOLTE SI É SENTITO PROPORRE DAL SCAFATO 
CRIMINALE PIERSILVIO BERLUSCONI E DALLA LESBICA PEDOFILA E NAZISTA MARINA 
BERLUSCONI, DI RICICLARE PER LORO, CENTINAIA DI MILIONI DI EURO MAFIOSI! 
SEMPRE EROICAMENTE RIFIUTANDO! A VOI IL GRANDISSIMO ANDREAS NIGG DI BANK J 
SAFRA SARASIN ZURIGO.

CIAO A TUTTI. SON SEMPRE IO, ANDREAS NIGG, EX MANAGER IN BANK VONTOBEL 
ZURIGO ED ORA MANAGER IN BANK J SAFRA SARASIN ZURIGO. SCHIFO CON TUTTE LE 
FORZE I PEDOFILI BASTARDI, SATANISTI, NAZISTI, SATA卐NAZISTI, ASSASSINI 
#BERLUSCONI! SON DEI FIGLI DI PUTTANONE E PEDOFILI! SON #HITLER, #PINOCHET 
E #PUTIN MISTI AD AL CAPONE, TOTO RIINA E PASQUALE BARRA DETTO "O ANIMALE"! 
SI PRENDONO LA NAZIONE INTERA, INTRECCIANDO POTERE ECONOMICO, POTERE DI 
CORROMPERE CHIUNQUE, POTERE MEDIATICO, POTERE EDITORIALE, POTERE SATANICO, 
POTERE FASCIOCIELLINO, POTERE MASSOMAFIOSO, POTERE DI TERRORISTI 
NAZIFASCISTI, POTERE RICATTATORIO, POTERE DI ASSASSINIO, POTERE STRAGISTA, 
POTERE DI INTELLIGENCE FOTOCOPIA DI OVRA E GESTAPO, ADDIRITURA PURE POTERE 
CALCISTICO ED IL POTERE DEI POTERI: IL POTERE POLITICO (OSSIA OGNI TIPO DI 
POTERE: OGNI)! CREANDO DITTATURA STRA OMICIDA! I TOPI DI FOGNA KILLER 
#SILVIOBERLUSCONI, #PIERSILVIOBERLUSCONI E #MARINABERLUSCONI HAN FATTO 
UCCIDERE IN VITA LORO, ALMENO 900 PERSONE, QUASI SEMPRE PER BENISSIMO! LA 
LORO SPECIALITÁ É ORGANIZZARE OMICIDI MASSONICI! OSSIA DA FAR PASSARE PER 
FINTI SUICIDI, MALORI, INCIDENTI (VEDI COME HANNO UCCISO LENTAMENTE, IN 
MANIERA MASSONICISSIMA, LA GRANDE #IMANEFADIL, MA PURE GLI AVVOCATI VICINI 
A IMANE FADIL, #EGIDIOVERZINI E #MAURORUFFFINI, MA ANCHE TANTISSIMI 
MAGISTRATI GIOVANI CHE LI STAVANO INDAGANDO, SEGRETAMENTE O NON, COME 
#GABRIELECHELAZZI, #ALBERTOCAPERNA, #PIETROSAVIOTTI, #MARCELLOMUSSO, 
#FRANKDIMAIO, PER NON DIRE DI COME HAN MACELLATO GLI EROI #GIOVANNIFALCONE 
E #PAOLOBORSELLINO)! IL TUTTO IN COMBUTTA CON SERVIZI SEGRETI NAZIFASCISTI, 
BASTARDA MASSONERIA DI ESTREMA DESTRA (VEDI #P2 P2 O #LOGGIADELDRAGO LOGGIA 
DEL DRAGO, OSSIA LOGGIA PERSONALE DEL PEZZO DI MERDA PEDOFILO E STRAGISTA 
#SILVIOBERLUSCONI). OLTRE CHE IN STRA COMBUTTA CON LORO VARIE COSA NOSTRA, 
CAMORRA, NDRANGHETA, MAFIA RUSSA, MAFIA CINESE, MAFIA COLOMBIANA, MAFIE DI 
TUTTO IL PIANETA TERRA.

OGGI VORREI SCRIVERE PURE, DI QUEL TOPO DI FOGNA CORROTTISSIMO, ANZI 
"BERLUSCORROTTISSIMO", CHE É IL GIUDICE PIÚ PREZZOLATO DEL MONDO: 
#MARCOTREMOLADA DEL RUBY TER! MASSONE DI MERDA DI MILLE LOGGE D'UNGHERIA 
(MA PURE DI BULGARIA, CECOSLOVACCHIA E CAMBOGIA DI POL POT, TANTO CHE CI 
SIAMO, MEGLIO IRONIZZARCI SOPRA UN POCO, PLEASE). MERDA AMMAZZA GIUSTIZIA 
MARCO TREMOLADA DEL RUBY TER, NAZIFASCISTA CORROTTISSIMO DA SILVIO 
BERLUSCONI, PIERSILVIO BERLUSCONI E MARINA BERLUSCONI! STO VERME SGOZZA 
GIUSTIZIA DI #MARCOTREMOLADA (LO VEDETE QUI
https://l450v.alamy.com/450vfr/2ded6pm/milan-italie-30-novembre-2020-milan-ruby-ter-proces-a-la-foire-president-marco-tremolada-usage-editorial-seulement-credit-agence-de-photo-independante-alamy-live-news-2ded6pm.jpg
 
) É IL NUOVO #CORRADOCARNEVALE, #RENATOSQUILLANTE E #VITTORIOMETTA. ESSENDO 
IO, ANDREAS NIGG DI BANK J SAFRA SARASIN, STATO DEFINITO BANCHIERE SVIZZERO 
DELL'ANNO, SIA NEL 2018, 2019 E 2020 (MI DANNO TUTTI PER VINCITORE PURE NEL 
2021), HO FATTO LE MIE INDAGINI E SÓ PER STRA CERTO, CHE STO MASSONE 
NAZI卐FASCISTA PREZZOLATO A PALLONE, DI #MARCOTREMOLADA DEL #RUBYTER, HA GIÁ 
A DISPOSIZIONE, PRESSO 7 DIVERSI FIDUCIARI ELVETICI, 3 MLN DI €, RICEVUTI 
AL FINE DI INIZIARE AD AZZOPPARE IL PROCESSO RUBY TER (COME 
PUNTUALISSIMAMENTE ACCADUTO IL 3/11/2021). ALTRI 7 MLN DI € GLI 
ARRIVEREBBERO A PROCESSO COMPLETAMENTE MORTO. MI HA CONFERMATO CIÓ, PURE IL 
VERTICE DEI SERVIZI SEGRETI SVIZZERI (CHE ESSENDO SEGRETI, MI HAN IMPOSTO 
DI NON SCRIVERE NOMI E COGNOMI, COSA CHE DA BANCHIERE SPECCHIATO, RISPETTO) 
ED IL GRAN MAESTRO DELLA GRAN LOGGIA SVIZZERA: #DOMINIQUEJUILLAND. 
D'ALTRONDE, SE ASCOLTATE SU #RADIORADICALE, TUTTE LE UDIENZE DEL PROCESSO, 
AHIMÉ FARSA, #RUBYTER, VEDRETE CHE STA MERDA CORROTTA, NAZISTA E NEO 
PIDUISTISSIMA DI #MARCOTREMOLADA DEL RUBY TER STESSO (GIUDICE CORROTTO DA 
SCHIFO, DI 1000 LOGGE D'UNGHERIA, BULGARIA, CECOSLOVACCHIA E PURE DI 
CAMB

Re: [git-users] GITK: Useability issue, can't scroll through fie list ?

[Philip Oakley]

> 1. git gui does not have a link to gitk ? 
Use the top left  menu: Repository >> Visualise .. for the two gitk viewer 
options.

> _3_. clicking on right bottom view where it says "path"[sic] "tree" does 
not make gitk context aware. 

The gitk Patch[!] / Tree options will swap what is being displayed in the 
two bottom windows.

* for Patch the right hand side lists just the commit/'comment' file and 
the files which have diffs (changes).
The left hand window then shows those diffs and commit comment. Clicking an 
item in the right hand pane will make the left pane jump to the required 
place.

* for Tree, the righ hand side panels lists the full file tree that is 
present in the commit snapshot, with the commit comment at the top. 
Directories has a small blue triangle and can be expanded by clicking the 
triangle - watch where the 'arrow' of the triangle points.
Having selected a file/item in the right hand window, the left hand window 
then will display that selected file as a full raw text. Useful if the diff 
context isn't sufficient in Patch mode.

HTH.
Philip

On Thursday, December 2, 2021 at 10:07:39 AM UTC Konstantin Khomoutov wrote:

> On Wed, Dec 01, 2021 at 09:55:38PM -0800, skybuck2000 wrote:
>
> > I see two issues right now:
>
> [...]
>
> Please stop reporting bugs on this list.
>
> As I've suggested several times before, this list is dedicated to help
> inexperienced Git users solve the problems they have when using Git.
>
> Discussing usability issues or apparent bugs is just pointless here for the
> two reasons: 1) this list is not read by Git developers (who could try to 
> fix
> the code), and 2) no one else is going to report bugs for you.
>
> Please re-read .
>
>
> Oh, and while we're at it, one more kind request: please stop posting
> identical e-mails to both git-users and git-for-windows. Again, as I've
> suggested elsewhere, the former list is for discussing basic _generic_
> problems with Git - no matter which flavour it is and on which platform it
> runs on, - and the latter is for solving problems specific to Windows and
> Git-for-Windows as the de-facto standard ongoing port of Git to that 
> platform.
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/58f1006c-e53e-4b21-a5c2-a4350ca6c4bdn%40googlegroups.com.

[git-users] Re: Git branches vs Mercurial branches

[Mikko Rantalainen]

Was: [Mystery solved, I owe you an apology] (was: [git-users] how to
remove two commits from a remote server)

On Wed, Dec 1, 2021 at 12:18 PM Uwe Brauer  wrote:
> As I said I am one of the maintainer of
> matlab-mode(emacs), a git repository in sourceforge. Since I know
> mercurial relatively well but don't really understand git (to put it
> [...]
> It never occurred to me, that there would be two
> type of branches (in mercurial there is only one type of branch, it
> commits can be on remote or on local or on both but there is no need to
> distinguish both).
> Yes I know git branch -a shows branches, I never really understand them
> all.

I think this point deserves a bit further discussion.

As I wrote at https://stackoverflow.com/a/11223644/334451 it's
actually the other way around. Mercurial has multiple things that are
logically branches: unnamed branches, named branches and bookmarks.
Git only has branches but it uses namespaces for branch names
(basically path for a branch + the name). Git users often speak about
"master" branch (or "main" nowadays) and you have to decipher from the
context if they actually mean refs/heads/master or
refs/remotes/origin/master or something else. Git is also smart enough
to guess the correct path if you use just the last part of the full
name and in some context the interpretation of short names is
explicitly defined. For example, when you say

git push origin foo:bar

it will actually execute (assuming foo is local branch and not a tag)

git push origin refs/heads/foo:refs/heads/bar

which means 'take the local "refs/heads/foo" and push it to remote
server "origin" using name "refs/heads/bar" on the remote server'. You
can use commit SHA-1 for the source as long as the target is a branch
that already exists (otherwise git cannot know if you want to create a
new tag or branch). I prefer to use this syntax if I ever need to
force (overwrite) things on the remote server so that I can accurately
specify the new state of the target branch.

As everything actually has full namespaced name ("refname"), you can
also do stuff like having branch master (actually refs/heads/master)
and tag master (actually refs/tags/master) but that's just asking for
trouble. Git always uses the full refnames under the hood but allows
using shorter names in the user interface.

By default, when you run "git branch" it lists only refs/heads/*
without the full "refname". For full branch names you have to run
something like

git branch --format="%(refname)"

or for all branches, local or remote no matter how many remote servers
you've configured

git branch -a --format="%(refname)"

which will list full names of all the known branches. All those names
are actually file paths under the directory .git/refs/ in your working
directory so the whole system is actually really simple (the file at
the end of that path contains just the SHA-1 of the commit that's the
tip of that branch). When you "create a new branch" in Git, you
literally create one new file with 41 bytes containing the currently
checked out commit SHA-1 (output of "git rev-parse HEAD") with
trailing linefeed and the name of the file is the name of the branch
you created. The file .git/HEAD contains textual reference to
currently checked out commit or head or tag in your working directory.

Git tags are implemented similarly but those are stored in
.git/refs/tags/ and will not be automatically modified when you create
new commits. Note that tags are not kept in separate namespaces but
when you fetch changes, you automatically get all the tags, too, and
those are always in the prefix refs/tags/.

You can list all known tags with full refnames using command

git tag --format='%(refname)'

Note that "git tag -a" does exist but it doesn't mean "list all" but
"create annotated tag" (a tag that has more info attached to it
instead of just the name) because tags do not have namespaces, so
there's no need for "list all tags".

The branches starting with refs/remote/ will be updated automatically
when you run "git fetch" (or do "git pull" which will run "git fetch"
behind your back).

Git will be much easier to understand if you never ever use "git pull"
for anything.  Always run "git fetch" (or "git fetch --all" if you
have multiple remote servers) instead and it will only update the
refs/remote/ hierarchy only and download the required pack/object
files to actually know what all those SHA-1's mean. After you have
executed "git fetch" you can use "gitk --all", "gitg" or some other
repository viewer that can show both local and remote branches. If you
don't have any GUI tools, you can run something like

git log --oneline --decorate --graph --all

or (everything on one line)

git log --graph --all --pretty=format:"%C(auto)%h%d%Creset %s
%Cgreen(%cr)%Creset"

Then you can sanely decide if you want to merge, rebase or do something else.


As a party trick, you can also do stuff like

git push . HEAD:foo

which means p

Re: [git-users] Re: Command to display current branch tracking information ?

[Philip Oakley]

> Can this command be set up as an alias ? This would require to pass a 
parameter somehow ? 

yes it can be an alias, but because the branch name is inserted in the 
command line it need to be a shell alias passing in the branch name as $1.


On Thursday, December 2, 2021 at 11:30:49 AM UTC Philip Oakley wrote:

> > Sorry but what is {u} supposed to be? The url of the remote server? 
>
> The '@{u}' is a shorthand for '@{upstream}' typed exactly, that modifies 
> the given branch name to become the upstream of the given branch, and then 
> rev-parse finds its pretty name, and abbrev-ref trims off the leading part 
> of the "ref/./.". 
>
> Worth looking up "@" and its qualifiers ;-) 
>
> On Thursday, December 2, 2021 at 7:45:33 AM UTC o...@ucm.es wrote:
>
>> >>> "PO" == Philip Oakley  writes:
>>
>> > git rev-parse --abbrev-ref --symbolic-full-name @{u}
>> > Had to look it up yesterday. Then you need
>>
>> Sorry but what is {u} supposed to be? The url of the remote server?
>>
>> I tried out 
>> git rev-parse --abbrev-ref --symbolic-full-name master@{git+ssh://
>> o...@git.code.sf.net/p/matlab-emacs/src 
>> }
>>
>> Or 
>>
>> git rev-parse --abbrev-ref --symbolic-full-name master@{origin}
>>
>> None worked. I surely missed something essential.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/75776565-1e78-41b9-afd9-388bc430d58en%40googlegroups.com.

Re: [git-users] Re: Command to display current branch tracking information ?

[Philip Oakley]

> Sorry but what is {u} supposed to be? The url of the remote server? 

The '@{u}' is a shorthand for '@{upstream}' typed exactly, that modifies 
the given branch name to become the upstream of the given branch, and then 
rev-parse finds its pretty name, and abbrev-ref trims off the leading part 
of the "ref/./.". 

Worth looking up "@" and its qualifiers ;-) 

On Thursday, December 2, 2021 at 7:45:33 AM UTC o...@ucm.es wrote:

> >>> "PO" == Philip Oakley  writes:
>
> > git rev-parse --abbrev-ref --symbolic-full-name @{u}
> > Had to look it up yesterday. Then you need
>
> Sorry but what is {u} supposed to be? The url of the remote server?
>
> I tried out 
> git rev-parse --abbrev-ref --symbolic-full-name master@{git+ssh://
> o...@git.code.sf.net/p/matlab-emacs/src 
> }
>
> Or 
>
> git rev-parse --abbrev-ref --symbolic-full-name master@{origin}
>
> None worked. I surely missed something essential.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/0e58eb21-9368-477f-94e8-2817546b2b54n%40googlegroups.com.

Re: [git-users] GIT failed to checkout the linux kernel on a 6 GB system

[Konstantin Khomoutov]

On Wed, Dec 01, 2021 at 09:01:36PM -0800, skybuck2000 wrote:

> I would like to report that GIT failed to checkout the linux kernel on a 6 
> GB system.
> 
> For now I believe it ran out of memory. I only tried once.
> 
> PAGEFILE.SYS on this system was disabled.

[...]

Again:

 * Please do not post identical messages to the two mailing lists.

 * 99% of systems Git runs on do not have the concept of "PAGEFILE.SYS", and
   you do not even bother to think about this. Please do.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/20211202101630.epkentqleo62wwha%40carbon.

Re: [git-users] Re: GIT failed to checkout the linux kernel on a 6 GB system

[Konstantin Khomoutov]

On Wed, Dec 01, 2021 at 09:32:56PM -0800, skybuck2000 wrote:

>  It would be nice if GIT would respect the following limits:
> 
> new@new-PC MINGW64 /
> $ ulimit -a
> core file size  (blocks, -c) unlimited
> data seg size   (kbytes, -d) unlimited
> file size   (blocks, -f) unlimited
> open files  (-n) 256
> pipe size(512 bytes, -p) 8
> stack size  (kbytes, -s) 2036
> cpu time   (seconds, -t) unlimited
> max user processes  (-u) 256
> virtual memory  (kbytes, -v) unlimited

I doubt it could: what you see is Git Bash - being a port of Bash to Windows -
is implementing the shell built-in command `ulimit`. This shell builtin only
has sense on Unix-like systems because there it interacts with the POSIX
syscalls getrlimit/setrlimit which do not exist on Windows, where Git Bash
works. (And even there on POSIX-like systems, not all features exposed by
`ulimit` are actually enforced; for instance, on Linux, you can tweak the
"maximum RSS" limit but it is ignored; other systems have their own quirks).

> Then I could try and set these limits, however I fear if I set them now it 
> will limit GIT even more and it will lead to even sooner crashes... though 
> it's worth a try to see what happens.

I would guess tweaking them would not affect anything.

[...]

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/20211202101456.aznmgbjir773ldma%40carbon.

Re: [git-users] GITK: Useability issue, can't scroll through fie list ?

[Konstantin Khomoutov]

On Wed, Dec 01, 2021 at 09:55:38PM -0800, skybuck2000 wrote:

> I see two issues right now:

[...]

Please stop reporting bugs on this list.

As I've suggested several times before, this list is dedicated to help
inexperienced Git users solve the problems they have when using Git.

Discussing usability issues or apparent bugs is just pointless here for the
two reasons: 1) this list is not read by Git developers (who could try to fix
the code), and 2) no one else is going to report bugs for you.

Please re-read .


Oh, and while we're at it, one more kind request: please stop posting
identical e-mails to both git-users and git-for-windows. Again, as I've
suggested elsewhere, the former list is for discussing basic _generic_
problems with Git - no matter which flavour it is and on which platform it
runs on, - and the latter is for solving problems specific to Windows and
Git-for-Windows as the de-facto standard ongoing port of Git to that platform.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/git-users/20211202100734.eciinhgpla662k7j%40carbon.