[git-users] Re: Feature Request: Recognizing which code belongs together and in what file and file segment it belongs.

[skybuck2000]

On Sunday, September 12, 2021 at 11:20:51 AM UTC+2 philip...@iee.email 
wrote:

> Have you looked at the various --pickaxe and other file-following options 
> that can be set to different levels of similarity for the tracking of such 
> splitting and changing.
>

No.
 

> Sometimes the real problem is that the 'local' feature branch policies 
> (i.e. your corporate way of doing things) can be in conflict with the 
> underlying Git (Linux/Linus) philosophies of small changes, short lived 
> branches, no mega-merges, etc. such that the apparent conflict resolutions 
> (or failure to detect code movement) is easy for the dev to use git (with 
> those extra parameters) to simply resolve the conflicts...
>
> I guess Git hopes that the dev provides the `deep learning [caffeine 
> fuelled?] neural brain`.. ;-)  while it provides some aggressive tools to 
> follow those splits.
>
> Also look out for the discussions on the Git mailing list for the 
> forthcoming ORT merge strategy (i.e. the `-sort` option ;-)
>
> https://blog.palantir.com/optimizing-gits-merge-machinery-part-v-46ff3710633e
>
> https://lore.kernel.org/git/CABPp-BGR3dfJE7TZ+jkjDdWyeXYowmJhtoFaQ8_Abn=zro...@mail.gmail.com/
>  
> 
>  
> (as a starter)
>
> If you have some shareable examples then the author of ORT would be 
> interested in those tricky cases. 
>

In the past I tried this:

https://www.reddit.com/r/git/comments/kjcdyz/git_split_file_into_multiple_files_then_detect/

With some splitting techniques from somebody at microsoft.

These splitting techniques provided not to be sufficient.

Perhaps the example is to simple. 

Perhaps code recognition and deep learning is too difficult and too CPU 
expensive.

One possible idea that comes to mind inspired by your post is to allow a 
developer to manual specify "code segments" in the original file and where 
changes inside those code segments should go to which file.

So for example a file could be "marked-up" as follows:


[begin of split into file1.c]

some code

[end of split into file1.c]

[begin of split into file2.c]


[end of split into file2.c]

[begin of split into file3.c]


[end of split into file3.c]

These mark ups could be put into a copy of the original fork file stored on 
the child fork file.

Then git ignores these markups... but does understand better where parts of 
the original fork file should go into the child fork file.

That should make it possible for git to improve it's splitting capabilities.

This feature request allows more freedom for child forks to work they way 
the want to work.

Later vice versa could be done as well if changes want to be send back to 
the original fork file.

If you believe something like this can be done with --pickaxe or other git 
options give some examples or some links to further documentation.

So far I have not yet found any good information about this.

I am looking for something that can handle large files and multiple lines 
of splitting code... not just a single line.


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/bcf9ea8f-6f7e-4f5d-b934-67898bd73c0cn%40googlegroups.com.

[git-users] Feature Request: Recognizing which code belongs together and in what file and file segment it belongs.

[skybuck2000]

Problem description:

Background:
Original fork does not want to split a file.
Child fork does want to split the file and does so.
Child fork can no longer benefit from changes from original fork.

Problem:
Git is incapable of transferring the changes of orignal fork file to child 
fork splitted files.

Suggested Solution:
Use deep learning networks and machine learning to develop a neural brain 
which is capable of detecting which changes/pieces of code belong together 
and in what file they belong.

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/e1795b1b-c690-403a-bb15-c7524313b783n%40googlegroups.com.

Re: [git-users] Re: Feature Request: Recognizing which code belongs together and in what file and file segment it belongs.

[skybuck2000]

>
>
> Even better would be the compiler's parser for the code that would just 
> split out the major 'functional' segments that the code syntax already 
> defines. 
>
>
I agree with this assessment that having a compiler which can spit out meta 
data about code or some kind of API to understand code structure would be 
very valuable and usefull to have.

Unfortunately for the end user of Delphi so far it's mostly focused on 
compiling code.

However there is also an in-memory compiler which is probably responsible 
for filling in GUI components like class explorer, structure and other 
insights.

So it seems Delphi at least already has these capabilities, but as far as I 
know only available for GUI.

However it is possible to write extension of Delphi, for example GExpert.

Perhaps such an extension could be used/abused to do some more interesting 
things like split up code into seperate files automatically.

And also introduce uses clausules automatically.

Doing this restructuring project/experiment I felt more like a compiler 
than  a human being ! =D

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/8976ca44-ab2b-4d6a-9e68-a2b86b502d8dn%40googlegroups.com.

[git-users] Re: Feature Request: Recognizing which code belongs together and in what file and file segment it belongs.

[skybuck2000]

Here is a "real-world" example:

The original repository is this one:
https://github.com/PascalCoin/PascalCoin

My restructured repository is this one:
https://github.com/SkybuckFlying/PascalCoinRestructured

The original repository is a big mess and it's very hard to find any class 
in it. 

While the restructured repository is splitted into folders and more files, 
a bit like java where each class is in it's own file.

By restructuring classes into folders and files it becomes much easier to 
find those classes in the project manager.

No other option exists in Delphi to find classes through the entire project 
besides "search in all files" this however requires to know what you are 
searching for in the first place which is less ideal but ok.

Anyway. Now PascalCoin original repository has "advanced" there is more new 
code in some of the files that were splitted.

It would be interesting if there was a way to incorporate those changes 
into the restructured folders/files.

There seem to be many possibilities to only selectively choose what changes:

For example:
https://stackoverflow.com/questions/449541/how-can-i-selectively-merge-or-pick-changes-from-another-branch-in-git

The one that looks somewhat promising is the diff to patch file option 
where a patch is created.

Then the patch could be applied to some file.

I haven't tried this yet, though I see some down sides... 

First of all the current changes are many, second I would need to know and 
specify where these changes/patches need to go to what file. 
This gets a bit difficult to automate, hence my suggestion for tags in the 
files themselfes or some other technique to specify what goes where.

The idea of "hunks" or interactive mode also sounds a little bit 
interesting.

Anyway if you take a look at both repositories can you make any 
recommendations how to apply the changes from original to restructured in 
an efficient way as possible ?

I do admit that I changed a whole bunch of stuff at the same time without 
making many commits. At the time I made those changes I wasn't really used 
to git that much.

I am used to working incredibly fast and making many changes if necessary 
and therefore git may not entirely fit with my coding experiences which is 
incredibly fast.

Making many small commits would slow my development down drastically. 
Describing each little change for example would also require a lot of time. 
This workflow style of small little commits could be tried but at great 
expense to me and I am not sure if that would be worth it at all and if it 
is the way forward.

I doubt this will be any use to the current situation. A possibility is to 
try and work together with original repository owner and apply 
restructuring there, but then I would loose the already done work.

For git it doesn't really matter if it's small or big changes/commits. It 
can either recgonize chunks or not, it knows where to put them or not.

I am willing to go through some kind of big interactive mode or something 
to try and incorporate the changes from the original to the restructured 
repository just to see if it can be done with git.

So what I am looking for is any assistance from git commands, tricks, 
scripts, tools or anything to basically do the following:

git init
git remote add Restructured 
https://github.com/SkybuckFlying/PascalCoinRestructured
git remote add PascalCoin https://github.com/PascalCoin/PascalCoin
git fetch Restructured
git fetch PascalCoin
git merge Restructured/master
git merge PascalCoin/master
^
above command may have to be something different more advanced ???

Right now this seems to produce many merge conflicts and original files are 
imported back again, instead of split into already existing files... 

Bye for now.
  Skybuck.
On Sunday, September 12, 2021 at 3:09:20 AM UTC+2 skybuck2000 wrote:

> Problem description:
>
> Background:
> Original fork does not want to split a file.
> Child fork does want to split the file and does so.
> Child fork can no longer benefit from changes from original fork.
>
> Problem:
> Git is incapable of transferring the changes of orignal fork file to child 
> fork splitted files.
>
> Suggested Solution:
> Use deep learning networks and machine learning to develop a neural brain 
> which is capable of detecting which changes/pieces of code belong together 
> and in what file they belong.
>
> 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/2ce32d3e-620d-4188-8890-84f46d413861n%40googlegroups.com.

[git-users] Re: Feature Request: Recognizing which code belongs together and in what file and file segment it belongs.

[skybuck2000]

Vice versa could also be interesting:

git init
git remote add Restructured 
https://github.com/SkybuckFlying/PascalCoinRestructured
git remote add PascalCoin https://github.com/PascalCoin/PascalCoin
git fetch Restructured
git fetch PascalCoin
git merge PascalCoin/master
git merge Restructured/master

Trying to apply the restructured situation to the old one.

Not sure if it matters much... 

Ofcourse this would be applying old code to new code with risks of old code 
replacing new code which is not good ofcourse.

But maybe this will somehow apply the restructured folders/files.

Worthy of a test to see what happens

>From what I can tell it does the same thing more or less :) same merge 
conflicts... any suggestions how to do this better ?

Bye for now,
  Skybuck.


On Thursday, October 7, 2021 at 4:41:05 AM UTC+2 skybuck2000 wrote:

> Here is a "real-world" example:
>
> The original repository is this one:
> https://github.com/PascalCoin/PascalCoin
>
> My restructured repository is this one:
> https://github.com/SkybuckFlying/PascalCoinRestructured
>
> The original repository is a big mess and it's very hard to find any class 
> in it. 
>
> While the restructured repository is splitted into folders and more files, 
> a bit like java where each class is in it's own file.
>
> By restructuring classes into folders and files it becomes much easier to 
> find those classes in the project manager.
>
> No other option exists in Delphi to find classes through the entire 
> project besides "search in all files" this however requires to know what 
> you are searching for in the first place which is less ideal but ok.
>
> Anyway. Now PascalCoin original repository has "advanced" there is more 
> new code in some of the files that were splitted.
>
> It would be interesting if there was a way to incorporate those changes 
> into the restructured folders/files.
>
> There seem to be many possibilities to only selectively choose what 
> changes:
>
> For example:
>
> https://stackoverflow.com/questions/449541/how-can-i-selectively-merge-or-pick-changes-from-another-branch-in-git
>
> The one that looks somewhat promising is the diff to patch file option 
> where a patch is created.
>
> Then the patch could be applied to some file.
>
> I haven't tried this yet, though I see some down sides... 
>
> First of all the current changes are many, second I would need to know and 
> specify where these changes/patches need to go to what file. 
> This gets a bit difficult to automate, hence my suggestion for tags in the 
> files themselfes or some other technique to specify what goes where.
>
> The idea of "hunks" or interactive mode also sounds a little bit 
> interesting.
>
> Anyway if you take a look at both repositories can you make any 
> recommendations how to apply the changes from original to restructured in 
> an efficient way as possible ?
>
> I do admit that I changed a whole bunch of stuff at the same time without 
> making many commits. At the time I made those changes I wasn't really used 
> to git that much.
>
> I am used to working incredibly fast and making many changes if necessary 
> and therefore git may not entirely fit with my coding experiences which is 
> incredibly fast.
>
> Making many small commits would slow my development down drastically. 
> Describing each little change for example would also require a lot of time. 
> This workflow style of small little commits could be tried but at great 
> expense to me and I am not sure if that would be worth it at all and if it 
> is the way forward.
>
> I doubt this will be any use to the current situation. A possibility is to 
> try and work together with original repository owner and apply 
> restructuring there, but then I would loose the already done work.
>
> For git it doesn't really matter if it's small or big changes/commits. It 
> can either recgonize chunks or not, it knows where to put them or not.
>
> I am willing to go through some kind of big interactive mode or something 
> to try and incorporate the changes from the original to the restructured 
> repository just to see if it can be done with git.
>
> So what I am looking for is any assistance from git commands, tricks, 
> scripts, tools or anything to basically do the following:
>
> git init
> git remote add Restructured 
> https://github.com/SkybuckFlying/PascalCoinRestructured
> git remote add PascalCoin https://github.com/PascalCoin/PascalCoin
> git fetch Restructured
> git fetch PascalCoin
> git merge Restructured/master
> git merge PascalCoin/master
> ^
> above command may have to be something different more advanced ???
>
> Right now this seems to produce many merge 

[git-users] Re: Feature Request: Recognizing which code belongs together and in what file and file segment it belongs.

[skybuck2000]

There is the class explorer in Delphi, never used it much, just tried it 
after a few clicks it crashes the IDE.

Relieing on IDE to make sense of source code is a bad idea anyway. Source 
code should be editable and easily searchable by windows explorer/textpad 
any editor or file exploration tool.

For more robustness/options of working with that source, especially as 
backup tools in case of IDE failures or other reasons. 

I have no idea how PascalCoin edits his files with huge scrollbars, 
crashing class explorers, and so forth. Perhaps other tools =D

Or he just knows from memory where everything is =D

I feel sorry for the man, he's making life very difficult for himself ! ;)

Bye,
  Skybuck =D

On Thursday, October 7, 2021 at 4:41:05 AM UTC+2 skybuck2000 wrote:

> Here is a "real-world" example:
>
> The original repository is this one:
> https://github.com/PascalCoin/PascalCoin
>
> My restructured repository is this one:
> https://github.com/SkybuckFlying/PascalCoinRestructured
>
> The original repository is a big mess and it's very hard to find any class 
> in it. 
>
> While the restructured repository is splitted into folders and more files, 
> a bit like java where each class is in it's own file.
>
> By restructuring classes into folders and files it becomes much easier to 
> find those classes in the project manager.
>
> No other option exists in Delphi to find classes through the entire 
> project besides "search in all files" this however requires to know what 
> you are searching for in the first place which is less ideal but ok.
>
> Anyway. Now PascalCoin original repository has "advanced" there is more 
> new code in some of the files that were splitted.
>
> It would be interesting if there was a way to incorporate those changes 
> into the restructured folders/files.
>
> There seem to be many possibilities to only selectively choose what 
> changes:
>
> For example:
>
> https://stackoverflow.com/questions/449541/how-can-i-selectively-merge-or-pick-changes-from-another-branch-in-git
>
> The one that looks somewhat promising is the diff to patch file option 
> where a patch is created.
>
> Then the patch could be applied to some file.
>
> I haven't tried this yet, though I see some down sides... 
>
> First of all the current changes are many, second I would need to know and 
> specify where these changes/patches need to go to what file. 
> This gets a bit difficult to automate, hence my suggestion for tags in the 
> files themselfes or some other technique to specify what goes where.
>
> The idea of "hunks" or interactive mode also sounds a little bit 
> interesting.
>
> Anyway if you take a look at both repositories can you make any 
> recommendations how to apply the changes from original to restructured in 
> an efficient way as possible ?
>
> I do admit that I changed a whole bunch of stuff at the same time without 
> making many commits. At the time I made those changes I wasn't really used 
> to git that much.
>
> I am used to working incredibly fast and making many changes if necessary 
> and therefore git may not entirely fit with my coding experiences which is 
> incredibly fast.
>
> Making many small commits would slow my development down drastically. 
> Describing each little change for example would also require a lot of time. 
> This workflow style of small little commits could be tried but at great 
> expense to me and I am not sure if that would be worth it at all and if it 
> is the way forward.
>
> I doubt this will be any use to the current situation. A possibility is to 
> try and work together with original repository owner and apply 
> restructuring there, but then I would loose the already done work.
>
> For git it doesn't really matter if it's small or big changes/commits. It 
> can either recgonize chunks or not, it knows where to put them or not.
>
> I am willing to go through some kind of big interactive mode or something 
> to try and incorporate the changes from the original to the restructured 
> repository just to see if it can be done with git.
>
> So what I am looking for is any assistance from git commands, tricks, 
> scripts, tools or anything to basically do the following:
>
> git init
> git remote add Restructured 
> https://github.com/SkybuckFlying/PascalCoinRestructured
> git remote add PascalCoin https://github.com/PascalCoin/PascalCoin
> git fetch Restructured
> git fetch PascalCoin
> git merge Restructured/master
> git merge PascalCoin/master
> ^
> above command may have to be something different more advanced ???
>
> Right now this seems to produce many merge conflicts and original files 
> are imported back again, instead of spli

[git-users] OT: Windows 7 + VMWARE15 + Windows 11 = LOST FILES !

[skybuck2000]

Some of you may be in a complex environment like described in the subject 
line.
I have reason to believe that there might be a file copieing problem 
between w7 and vmware and w11, thus before you start blaming GIT for losing 
files, first read carefully about the underlieing technology NTFS in case 
GIT is used on such windows systems.
GIT is ofcourse only as reliable as the underlieing file system and there 
is now a "UFO" incident spotted by me. This is "HOT" of the press. I just 
witnessed/tested it once and it failed spectacularly. I have had NO TIME to 
test it again, though I feel confident that subsequent testing will prove 
the issue is VERY REAL at least for the leaked windows 11 versions. There 
are also other reports of windows 11 official version having some kind of 
file system problem. Anyway the problem I witnessed I consider very severe 
for windows 7 users, trying windows 11 out inside virtual machines through 
VMWARE15.

I bring out this report as soon as possible to prevent anybody from losing 
files. I would hate to loose files myself like this that would suck.

All you need to know right now is:
1. Do not copy files between windows 7 and windows 11 until this is fully 
investigated, especialy if VMWare or other VM technology is in play/being 
used.

2. Do not repair windows 11 NTFS if that is the only copy of the data, for 
example user believed the copy was good and the original was deleted. The 
copy will be destroyed by the windows 11 disk repair tool ?!?!.

I just discovered a problem with windows 7 + vmware15 + windows 11. 

Windows 7 home runs on laptop build in harddisk C: 
VMWare15 Workstation/Player runs on Windows 7. 
Windows 11 leaked version runs on VMWare15 (can be mapped to Z: when 
offline) 
USB Portable Harddisk connected to laptop: E: 
Virtual Music Disk is on USB Portable Harddisk: F: 

Windows 11's virtual disk image was mapped Z: so it becomes accessible to 
Windows 7 via VMWare15's mapping feature. 

The goal was to copy a "demo" from F: to Z: 
(The reason was to run the demo in windows 11 because the demo would not 
run in windows 7 because python version 3.9 does not run on windows 7.) 

I did so by first creating Z:\Test 
Then I copied & paste "demo" folder to Z:\Test 

I already had a bad feeling about this because of two reasons: 
VMWare15 does not know about Windows 11 so how can it know about any 
possibly new NTFS data structures on disk ? 
Windows 7 might be using an older version of NTFS ?!? 

Anyway I continued to "trust" Microsoft W7, VMware15 and Microsoft W11 that 
they somehow found a way to "backwards compatible" copy files from Windows 
7 to Windows 11 via VMWare mapping feature. 

BUT NOPE. MY HUNCH WAS RIGHT AND MY TRUST BETRAYED. 

Something during the copieing process from W7 to W11 went wrong. 
When W11 booted in VMWare the copied files were not there. 
W11 wanted to repair the W11 disk. 
After repairing the W11 disk the files still not there. 

THUS THIS IS A SPECTACULAR FAILURE OF WINDOWS AND VMWARE SOFTWARE TO COPY 
FILES ! (AND WASTE USER TIME WITH DISK REPAIRS fortunately for me just 20 
GB W11 disk) 

FURTHER MORE THE W11 TOOL PROBABLY DELETED ANY COPIED FILES. 

IF USER BELIEVED FILES WERE SAFELY COPIED AND ORIGINALS WERE DELETED BY 
USER THEN REAL DATA LOSS COULD OCCUR ! 

Anyway this was just a simply test case for me to see what would happen. 
I decided to copy this demo software from W7 to W11 because python 3.9 does 
not run on W7 that's how I found out of this copieing problem. 

Now there are some un-answered questions and this is where you can help out 
to shine some serious light on this very serious situation: 

1. First question on my mind is: 

Is this problem/failure repeateably on the "official windows 11 release" 
which just happened a few days ago ?!?!? Can you repeat the problem ? 

2. Second question on my mind is: 

Does this problem/failure only occur through virtual machines ? For example 
W11 running in virtual machine ? Is it maybe a VMWare issue ? 

3. Is the failure caused by VMWare15 and if so are higher versions working 
correctly ? 

4. What if a real windows 11 NTFS harddisk is hooked up to an older Windows 
7 operating system and the older Windows 7 operating system starts creating 
and copieing files to W11 NTFS will this cause the same problems ? 

5. Could it be USB Portable driver related ? 

6. Could it be virtual harddisk VHD related ? (Never had a problem before) 
(vmware uses a different file format *.vmsomething) 

The windows 11 virtual disk is also on the E: drive/usb portable, this 
should not matter ?!?! 

This is a very suspicious and very alarming situation ! 

One question which would blow my mind: 

7. What happens if it's VICE VERSA ?!?!? 

What if real windows 11 os/machine is hooked up to a windows 7 harddisk and 
files/folders are copied from windows 11 to windows 7, could this NUKE the 
windows 7 NTFS file system ?!?!?!? 

^^^ Now I am starting to worry because this should have been 

[git-users] Make git aware of which machine did the git commits ?

[skybuck2000]

Hello,

Right now I am working with git on two different machines:
Windows 7 on real hardware.
Windows 11 on a virtual machine.

It would be cool if git could be made aware somehow on which machine the 
commits were made ?

Right now the windows 7 machine uses Skybuck Flying
Right now the windows 11 machine uses my e-mail addres ???

So that is my second less important question why is windows 11 using my 
e-mail and not my github account ? Hmmm... now github stats are kinda 
ruined a bit...

Is there still a way to correct that ?

Would be cool if both can be done.

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/1d3d4ea7-1f87-4d8a-b8be-bdb2654ee6d5n%40googlegroups.com.

[git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

On Thursday, December 16, 2021 at 10:14:58 AM UTC+1 Erik Cervin Edin wrote:

> Personally, I would use different email in the different environments and 
> take advantage of that (at least gmail) strips trailing parts of the email
>
> git config --global user.email foo+...@gmail.com
> git config --global user.email foo+...@gmail.com
>
> To claim GitHub stats, I would associate the emails with my GitHub profile
>

Neat solution.

I do worry about another thing though, other users of the repository would 
see two different e-mail addresses, that might worry or confuse them, 
especially if they want to write some recgonize script and don't realise 
there are two e-mail addresses.

They may also start wondering if one is real and the other one fake !

But besides from that neat solution ! Does require some extra setup from 
github... I wasn't sure if that was possible, so for now I believe you ! ;)

It does give some e-mail redundancy... however it might also be 
risky/annoying, what if some day github requires two real e-mail addresses 
and if it's not real it will decide that one was fake and starts deleting 
commits or locks you out or something...

E-mail is kinda special... also I see another problem with this solution, 
if the e-mail addresses are fake and somebody tries to reach you it won't 
work.

Also google groups prevents me from seeing your actual solution, I don't 
really see your solution.

I only see foo..

So I assume you encoded your machine somehow into the e-mail address.

Try and explain it one more time, but don't use the @ sign because that 
makes the google bot trip up and hide the information in some stupid link.

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/2dbdcd32-8f2a-4ae5-a721-15baba7ea323n%40googlegroups.com.

[git-users] Re: how to remove two commits from a remote server

[skybuck2000]

>
> commit 89346f81fef27286bd3fb1ed3ddc94a6f3fb560d (origin/copyright, 
> origin/copy) 
> | Author: Uwe Brauer  
> | Date: Thu Nov 25 10:43:56 2021 +0100 
> | 
> | Add patches to my new branch 
> | 
> | --HG-- 
> | branch : copyright 
> | 
> * commit 66380013003549a6851d4e110b29a5a439e05609 
> | Author: Uwe Brauer  
> | Date: Mon Nov 22 21:51:13 2021 +0100 
> | 
> | Add patches to a special, named branch! 
> | 
> | --HG-- 
> | branch : copyright 
> | 
> * commit c945bf50251150e0d4ad7ee751c7e9615cb4b3e8 (origin/master, 
> origin/HEAD) 
> | Author: Uwe Brauer  
> | Date: Mon Nov 22 09:33:48 2021 +0100 
> | 
> | Correct a silly typo in company-matlab-shell.el 
> | 
> | * company-matlab-shell.el: 677 correct a silly typo: Auctex should be 
> Matlab 
>
>
> The first two commits I should have pushed.


This is confusing, do you mean the top two ? or the bottom two ?

I will discuss both possibilities and explain how I would do it the easy 
way.

With easy I mean easy to remember and execute.

Situation Top Two, both copyright statements:

git checkout 
git branch newbase

git checkout 
git branch moveme

git checkout 
git branch splitpoint

(splitpoint could be same as newbase)

git switch moveme
git rebase --onto newbase splitpoint moveme

that will skip over the bad commit and keep that one on a seperate branch
git checkout 
git branch badcommit
git branch -d badcommit

that should get rid of it.

git branch -m renametofinalbranchname

git push origin -f finalbranchname

overwrites/force pushes it to server

Situation bottom two:

easy 
git checkout 
git branch badcommit
git branch -d badcommit
git checkout 
git branch finalbranchname
or
git switch finalbranchname
git push origin -f finalbranchname

This is where GIT could use lots of work to make things easier:

git delete 

Should handle all of this automatically :)

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/dc3f4342-93f5-458a-9c0a-6e8abbda10a9n%40googlegroups.com.

[git-users] Re: git log --graph --all makes top line fall of screen.

[skybuck2000]

Reversing the log is a possible solution, it does look a little bit weird, 
commit hashes at the bottom and commit comments at the top per commit, but 
could be interesting:

git --no-pager log --all --graph --decorate --color=always | tac | sed -e 
's/[\]/aa/g' -e 's/[/]/\\/g' -e 's/aa/\//g' | less -r +G -X

for one line version:

git --no-pager log --all --graph --oneline --decorate --color=always | tac 
| sed -e 's/[\]/aa/g' -e 's/[/]/\\/g' -e 's/aa/\//g' | less 
-r +G -X

Found it here:

terminal - How to make git-log scroll up instead of down - Stack Overflow 


I wish I did not have to spent so much time fixing stupid bugs like this :P

Oh yeah and the aliases:

The corresponding git alias is

[alias] 

orlog = !"git --no-pager log --all --graph --decorate --oneline 
--color=always | tac | sed -e 's/[\\]/aa/g' -e 's/[/]//g' 
-e 's/aa///g' | less -r +G -X"
[alias] 
rlog = !"git --no-pager log --all --graph --decorate --oneline 
--color=always | tac | sed -e 's/[\\]/aa/g' -e 's/[/]//g' 
-e 's/aa///g' | less -r +G -X"

orlog for one line and reverse
rlog for reverse

or choose whatever alias you like ! ;)

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/17a89fdb-a710-46f5-b321-72ef0c1a8fc0n%40googlegroups.com.

[git-users] Re: git log --graph --all makes top line fall of screen.

[skybuck2000]

I am getting a small smile on my face ! =D

Powershell now looks pretty beautifull and distinsquashed.

I did it as follows:

changed the font to lucida console point size 12
changed screen background color to black
changed screen text to silver

the last change makes the commit hashes pop-out in white and the rest of 
the text in fainter white/grayish/silverish...

looks very beautifull.

Perhaps later I might investigate if it's possible to make the git commit 
hashes look yelllow, but I kinda like this white-ish look... it  feels more 
valuable... yellow feels more like PISS lol.

The only thing I still dislike somewhat is the red it's a bit too dark for 
origin/remote and such... but liveable.

Bye for now,
  Skybuck.

On Thursday, December 30, 2021 at 9:19:20 AM UTC+1 skybuck2000 wrote:

> LOLOLOLOLOLOLOL.
>
> POWERSHELL + GIT-POSH SOLVES IT !!!
>
> Q stays on the same line !
>
> HAHAHAHAHAHA MICROSOFT+POSH JUST OWNED YOU LINUX BITCHES.
>
> BUT NOW ALL IS WELL THE COLORS ARE A LITTLE BIT LESS BEAUTIFULL 
> CYBERPUNKY...
>
> MAYBE I CHANGE THAT LATER MAYBE NOT...
>
> CONTINUEING.
>
> 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/9d5f43ec-18f9-4107-ab20-bd869c418fbfn%40googlegroups.com.

Re: [SUBVERSION?] (was: [git-users] A more advanced git system with working trees per commit.)

[skybuck2000]

On Wednesday, December 29, 2021 at 2:57:31 PM UTC+1 o...@ucm.es wrote:

> >>> "s" == skybuck2000  writes: 
>
> > Now this is something to my liking. 
> > A git system where each commit and each branch has it's own working tree 
> ?! 
>
> Why don't you give subversion a try? Maybe you would be happier this way. 
>

https://subversion.apache.org/

Written by Apache ? No thanks ?!

Does it have log4j issues ! HAHA.

GIT has cool branching future.

I can't learn two systems, to much time...

Subversion may be akward... Git I can get and understand...

Git is the future maybe... it's still evolving.

With GIT I can scape it's feature perhaps... GIT is open source... has big 
man behind it from linux or at least that magic dust.

Who the F created subversion lol ?

Github is git git git no subversion.

What is the point still of subversion ?

I need something that can do it all.

This system I described may run into windows explorer limits.

Good thing I mention this... what is the limit of windows 11 explorer when 
it comes to path length... something I am going to find out soon.

Also is subversion open source ? Seeing apache I would guess yes...

I simply never looked into subversion that much... I don't think it's worth 
it any more... it's superceeded by git.

But if you disagreem then turn this discussion around and convince me 
somehow that subversion is better than git ! ;)

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/7e4ebd4d-1960-4e4c-9526-d781b5d027e3n%40googlegroups.com.

[git-users] Re: git log --graph --all makes top line fall of screen.

[skybuck2000]

Oops messed up that important alias, remove one line:

was:
[alias] 
rlog = !"git --no-pager log --all --graph --decorate --oneline 
--color=always | tac | sed -e 's/[\\]/aa/g' -e 's/[/]//g' 
-e 's/aa///g' | less -r +G -X"

should be:
[alias] 
rlog = !"git --no-pager log --all --graph --decorate --color=always | tac | 
sed -e 's/[\\]/aa/g' -e 's/[/]//g' -e 
's/aa///g' | less -r +G -X"

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/d02b064e-e534-4645-b34d-f8280d784bcan%40googlegroups.com.

[git-users] Re: git log --graph --all makes top line fall of screen.

[skybuck2000]

pascalcoin change " into '

still don't work when rlog or olog types,

output:


Skybuck@DESKTOP-0T9FP82 MSYS /usr/bin
$ alias
cd..='cd ..'
e:='cd e:'
ll='ls -l'
ls='ls -F --color=auto --show-control-chars'
olog='git --no-pager log --all --graph --decorate --oneline --color=always 
| tac | sed -e "s/[\\]/aa/g" -e "s/[/]//g" -e 
"s/aa///g" | less -r +G -X'
pascalcoin='cd e:\SourceCode\PascalCoinGit\PascalCoin'
rlog='git --no-pager log --all --graph --decorate --color=always | tac | 
sed -e "s/[\\]/aa/g" -e "s/[/]//g" -e 
"s/aa///g" | less -r +G -X'

Skybuck@DESKTOP-0T9FP82 MSYS /usr/bin
$ pascalcoin
sh: cd: e:SourceCodePascalCoinGitPascalCoin: No such file or directory

Skybuck@DESKTOP-0T9FP82 MSYS /usr/bin
$ e:

Skybuck@DESKTOP-0T9FP82 MSYS /e
$ cd SourceCode

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode
$ cd PascalCoinGit

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit
$ cd PascalCoin

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(ReCommit)
$ olog
sed: -e expression #3, char 17: unknown option to `s'
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
...skipping...
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(ReCommit)
$ rlog
sed: -e expression #3, char 17: unknown option to `s'
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
...skipping...
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(ReCommit)
$

Almost always something... to bad would have loved for this to work.. 
another 11 minutes wasted.

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/e917721e-cc9f-40a2-aeb0-f082d92e732an%40googlegroups.com.

Re: [SUBVERSION?] (was: [git-users] A more advanced git system with working trees per commit.)

[skybuck2000]

Path length hack for unlimited paths in windows 11.

Could come in very handy especialy if I want to start using worktrees which 
I most likely will have to go do to prevent stupid files ending up from git 
switching and also reducing then number of switches.

Apperently windows 11 is much worse than I thought, only 260 characters, 
that is peanuts.

So I definetly do not want to run into garbage like that.

So I immediately going to try this hack/modification:

Kinda sad I have to do so many modifications to software, takes up a lot of 
time, would hate to re-do it on a full blown new system, but alas such is 
life:

https://thegeekpage.com/make-windows-11-accept-file-paths-over-260-characters/

Make Windows 11 Accept File Paths over 260 Characters 

September 18, 2021 By Sambit Koley  

Windows 11 is configured to accept a file pathname to only 260 Characters 
(including the full folder name and the file name). Now, this cap over the 
nomenclature may seem fit for most of the users but what if that one time 
when you have a name a file that big? You simply can’t. Even if you try, 
Windows will stomp you with a “*Destination Path Too Long*” error message. 
Don’t worry. There is a pretty simple registry hack that you can use to get 
rid of this character limitations in Windows 11.

 
How to make Windows 11 accept File Paths over 260 Characters 

There is a sleek registry tweak that can manage this issue.

1. At first, press the* Windows key* and type “*regedit*“.

2. Then, click on “*Registry Editor*” from the search results.


 

 

*Warning *– Registry Editor is a sensitive location of the system. Before 
you create and modify a new key on your computer, we request to make a 
backup of the registry on your computer.

After opening the Registry Editor, click on “*File*“. Then click on “
*Export*” to back up the existing registry key on your system.

 

 

3. Now, on the left-pane, head down this way ~
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem 

 

4. Now, on the right-hand side, check if you can find the 
*“LongPathsEnabled”* value.

[

If you can’t find it, you have to create it on your own.

a. On the right-hand side, tap on the space and then click on the “*New>*” 
and click on “*DWORD (32-bit) Value*“.

 

 

b. Then, name the values as “*LongPathsEnabled*“.

]

5. Now, *double-click* on this “*LongPathsEnabled*” value to modify it.

 

 

6. Then, alter the ‘Value Data:’ to “*1*“.

7. Finally, click on “*OK*” to save the changes.



 

 

Once you have done completing this changes, close the Registry Editor. 
Then, restart your computer to save this changes.

That’s it! Now, there is no cap over the 260 characters in the naming 
process of a file/folder. You can name any file/folder up to any length you 
want.

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/ad534a1a-2beb-4535-90bf-62941a30a6e1n%40googlegroups.com.

[git-users] git diff confusing: still showing ^M at end of some lines.

[skybuck2000]

I am trying to get rid of ^M in repository cause it kinda looks weird and 
may screw up diffs, I am not exactly sure what is going on.

git diff head~2

I see red lines:
- text 
- text
- text
I see green lines
+ same text or slightly changed ^m
+ same text or slightly changed ^m
+ same text or slightly changed ^m

Why is git showing ^m ?

According to documentation when auto-crlf is set to true git should replace 
end of line markers with LF

so why is CR still showing up in git diff  ?!?!?

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/59ed8b98-c82a-46a9-b48c-400fa5f6615en%40googlegroups.com.

[git-users] Re: git log --graph --all makes top line fall of screen.

[skybuck2000]

For today I am fed up with mintty/git bash which is slow, and buggy as 
hell, and cmd.exe looks terrible and has no nice colors.

Time to try something else:

Windows 11 powershell and this:

posh-git by dahlbyk 

Maybe this will be better, time to find out ! =D

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/1c3a0f6d-9d2f-4b72-9cad-4201bf222665n%40googlegroups.com.

[git-users] Re: git log --graph --all makes top line fall of screen.

[skybuck2000]

LOLOLOLOLOLOLOL.

POWERSHELL + GIT-POSH SOLVES IT !!!

Q stays on the same line !

HAHAHAHAHAHA MICROSOFT+POSH JUST OWNED YOU LINUX BITCHES.

BUT NOW ALL IS WELL THE COLORS ARE A LITTLE BIT LESS BEAUTIFULL 
CYBERPUNKY...

MAYBE I CHANGE THAT LATER MAYBE NOT...

CONTINUEING.

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/0c83eaee-a8c4-4c91-b51e-16812de36cb8n%40googlegroups.com.

Re: [SUBVERSION?] (was: [git-users] A more advanced git system with working trees per commit.)

[skybuck2000]

OH MORE POTENTIAL TROUBLE AHEAD see what I mean...

A commenter mentioned this does not work on windows 11 ?!? It did work on 
Windows 10...

Well I am going to try it anyway...  need this to work.

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/b1bee08a-fe03-4f4f-9376-f104f26512c3n%40googlegroups.com.

[git-users] git log --graph --all makes top line fall of screen.

[skybuck2000]

The top line head-> and such falls of the screen in mintty.

This is kinda annoying, this makes me have to scroll up and down

scroll up to see head and other branch names
scroll down to see command line.

Is there a fix for this ?

So git log --graph --all
follow by
:Q

saves some lines at the bottom for the command prompt so the top doesn't 
fall off ?!?

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/8779c477-b95f-436f-9d3c-0b155ebb49e8n%40googlegroups.com.

[git-users] Re: git log --graph --all makes top line fall of screen.

[skybuck2000]

Unfortunately can't get this shit working, tried a whole bunch of things, 
another 30 minutes of my life wasted:

alias pascalcoin='cd e:\SourceCode\PascalCoinGit\PascalCoin"
alias rlog='git --no-pager log --all --graph --decorate --color=always | 
tac | sed -e "s/[\\]/aa/g" -e "s/[/]//g" -e 
"s/aa///g" | less -r +G -X'
alias olog='git --no-pager log --all --graph --decorate --oneline 
--color=always | tac | sed -e "s/[\\]/aa/g" -e "s/[/]//g" 
-e "s/aa///g" | less -r +G -X'


^ last attemptI tried to invert ' and "

sh: alias: --no-pager: not found
sh: alias: log: not found
sh: alias: --all: not found
sh: alias: --graph: not found
sh: alias: --decorate: not found
sed: -e expression #3, char 17: unknown option to `s'
There is no -^J option ("less --help" for help)
There is no no-pager option ("less --help" for help)
sed: -e expression #3, char 17: unknown option to `s'
There is no -^J option ("less --help" for help)
launch: No such file or directory
them: No such file or directory
through: No such file or directory
"winpty" may be a binary file.  See it anyway?
sh: /etc/profile.d/aliases.sh: line 25: syntax error near unexpected token 
`;;'
sh: /etc/profile.d/aliases.sh: line 25: `   ;;'

Skybuck@DESKTOP-0T9FP82 MSYS /usr/bin
$

Bye,
  Skybuck.
On Thursday, December 30, 2021 at 8:38:53 AM UTC+1 skybuck2000 wrote:

> Oops messed up that important alias, remove one line:
>
> was:
> [alias] 
> rlog = !"git --no-pager log --all --graph --decorate --oneline 
> --color=always | tac | sed -e 's/[\\]/aa/g' -e 's/[/]//g' 
> -e 's/aa///g' | less -r +G -X"
>
> should be:
> [alias] 
> rlog = !"git --no-pager log --all --graph --decorate --color=always | tac 
> | sed -e 's/[\\]/aa/g' -e 's/[/]//g' -e 
> 's/aa///g' | less -r +G -X"
>
> 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/0253e969-3992-4d6e-a9e8-34a62b43758an%40googlegroups.com.

[git-users] Re: GIT FUCKING SUCKS, ONE WORKING COPY IS NOT ENOUGH.

[skybuck2000]

ANOTHER NICE EXAMPLE WHY GIT SUCKS.

IT'S NOW COPIEING THE ENTIRE HISTORY.

NOOO MOTHERFUCKERS

I JUST NEED ONE FUCKING VERSION FUCKING IDIOTS LOL.

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/c3f51839-a549-48e0-8ca6-84aacab2b7dan%40googlegroups.com.

[git-users] Re: GIT FUCKING SUCKS, ONE WORKING COPY IS NOT ENOUGH.

[skybuck2000]

LISTEN UP YOU MOTHERFUCKERS

I JUST CREATED THIS FOLDER ON MY WINDOWS:

PascalCoinGit(For Copy Operations)

NOW BECAUSE LINUX/SH/BASH SUCKS SO MUCH I HAVE TO TYPE THIS COMPLETELY IN 
GIT BASH AND SHIT.

WORK ON TAB FEATURE SO IT IS AUTO-COMPLETED

OR UPGRADE/UPDATE GIT TO HAVE MULTIPLE WORKING TREES/FOLDERS

SOME LIKE:

WORKTREE1: Skybuck@DESKTOP-0T9FP82 MSYS 
/e/SourceCode/PascalCoinGit/PascalCoin (PascalCoinReducedAndSecured)
WORKTREE2: Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit(For 
Copy Operations)/PascalCoin (PascalCoinReducedAndSecured)
$

ALSO WHY THE FUCK YOU CALL IT TREE AND NOT FOLDER LIKE NORMAL PEOPLE LOL 
HAHAHA BUT OK.

TREE ACTUALLY MEANS A WHOLE BUNCH OF BRANCHES AND SHIT...

FOLDER ONLY SHOWS THE CURRENT ONE... NOT THE SUBFOLDERS DUH...

WORKTREE IS TOO ABSTRACT.


NOW I SHOULD BE ABLE TO SWITCH BETWEEN WORK TREES EASILY OR SOMETHING

GIT SWITCH TREE WORKTREE1
DO SOMETHING
GIT SWITCH TREE WORKTREE2
DO SOMETHING

BUT THE POINT IS... I MUST SEE BOTH WORKTREES 

WHY ?!

BECAUSE I DONT USE BEYOND COMPARE YET OR ANY OTHER ADVANCED EDITING TOOL.

A SIMPLE EDITOR SHOULD BE JUST FINE FOR SOURCE CODE AND SIMPLE OPERATIONS 
IN CASE COMPLEX EDITORS CRASH.

OKIDOKIE ?!

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/b0f30a25-dcfd-4297-8e19-291030054603n%40googlegroups.com.

[git-users] Re: GIT FUCKING SUCKS, ONE WORKING COPY IS NOT ENOUGH.

[skybuck2000]

ANOTHER REASON WHY GIT CLONE SUCKS IS IT IMPLIES A SERVER/GITHUB SOMEWHERE

FUCK THAT.

I SHOULD BE ABLE TO WORK LOCAL ONLY.

HOW THE FUCK I CLONE A GIT REPOSITORY

FROM LOCAL TO LOCAL

NEED MORE COMMANDS HAHAHAHAHAHAH

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/d6b35813-f310-445c-982b-d57b310d3553n%40googlegroups.com.

[git-users] GIT FUCKING SUCKS, ONE WORKING COPY IS NOT ENOUGH.

[skybuck2000]

ONE FUCKING WORKTREE ?!?!?!?

WHO THE FUCK ARE YOU EINSTEIN ?!?!?!?

YOU EDIT/MODIFY EVERYTHING PERFECTLY THE FIRST FUCKING TIME I DONT THINK SO 
MOTHERFUCKER.

I NEED MULTIPLE WORKING TREES.

LIKE ONE FOR 5 COMMITS AGO
LIKE ONE FOR 2 COMMITS AGO
LIKE ONE FOR NOW.

AND NO
 
I DONT WANT TO
CD.. 
CD..
GIT CLONE BLABLABLA
BECAUSE YOUR FUCKING CD.. COMMAND DONT WORK MOTHERFUCKER

CD .. DOES WORK MOTHERFUCKER

YOU WASTING MY TIME RE-TYPING COMMANDS.

YOU WASTING MY TIME BY NOT STORING MULTIPLE COMMITS IN SEPERATE FOLDERS FOR 
EASY ACCES AND EASY COPY & PASTE OPERATION.

CONSTANTLY SWITCHING BETWEEN  BRANCHES IS MORONIC.

I CANNOT SEE AND COPY AT THE SAME TIME.

I MUST SEE ONE BRANCH
GO BACK THE OTHER
DO A COPY
GO BACK AGAIN TO SEE BRANCH GET IT MOTHERFUCKER.

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/ea505994-e620-4ea6-b4ab-c92c2d09c190n%40googlegroups.com.

[git-users] Re: GIT FUCKING SUCKS, ONE WORKING COPY IS NOT ENOUGH.

[skybuck2000]

MIGHT AS WELL COPY THE ENTIRE REPO... IDIOTS ON THE INTERNET TELLING PEOPLE 
TO USE GIT CLONE FOR THAT HAHAHAH STUPID.


DO YOU SEE NOW WHY COPY & PASTE IS SUPERIOR.

I BET YOU DONT EVEN HAVE A COMMAND FOR IT IN GIT

GIT COPY
GIT PASTE

FUCK YOU

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/2190b8b3-702e-423c-a85e-64d6ab9f539en%40googlegroups.com.

[git-users] Re: GIT FUCKING SUCKS, ONE WORKING COPY IS NOT ENOUGH.

[skybuck2000]

SOME IDIOT ON THE INTERNET MENTIONED TO USE WORKTREE COMMAND I BET THAT 
OVERWRITES THE DEFAULT AND FUCKS UP PEOPLE REPOSITORY, PRETTY FUCKING 
STUPID...

BUT IT DOES APPEAR GIT HAS SUPPORT FOR MULTIPLE WORKING TREES:

Git - git-worktree Documentation (git-scm.com) 


FINALLY.

NAME

git-worktree - Manage multiple working trees
SYNOPSIS
git worktree add [-f] [--detach] [--checkout] [--lock [--reason ]] 
[-b ]  [] git worktree list [--porcelain] git 
worktree lock [--reason ]  git worktree move  
 git worktree prune [-n] [-v] [--expire ] git worktree 
remove [-f]  git worktree repair […​] git worktree unlock 

DESCRIPTION

Manage multiple working trees attached to the same repository.

A git repository can support multiple working trees, allowing you to check 
out more than one branch at a time. With git worktree add a new working 
tree is associated with the repository. This new working tree is called a 
"linked working tree" as opposed to the "main working tree" prepared by 
git-init[1]  or git-clone[1] 
. A repository has one main working 
tree (if it’s not a bare repository) and zero or more linked working trees. 
When you are done with a linked working tree, remove it with git worktree 
remove.

In its simplest form, git worktree add  automatically creates a new 
branch whose name is the final component of , which is convenient if 
you plan to work on a new topic. For instance, git worktree add 
../hotfix creates new branch hotfix and checks it out at path ../hotfix. To 
instead work on an existing branch in a new working tree, use git worktree 
add  . On the other hand, if you just plan to make some 
experimental changes or do testing without disturbing existing development, 
it is often convenient to create a throwaway working tree not associated 
with any branch. For instance, git worktree add -d  creates a new 
working tree with a detached HEAD at the same commit as the current branch.

If a working tree is deleted without using git worktree remove, then its 
associated administrative files, which reside in the repository (see 
"DETAILS" below), will eventually be removed automatically 
(see gc.worktreePruneExpire in git-config[1] 
), or you can run git worktree 
prune in the main or any linked working tree to clean up any stale 
administrative files.

If a linked working tree is stored on a portable device or network share 
which is not always mounted, you can prevent its administrative files from 
being pruned by issuing the git worktree lock command, optionally 
specifying --reason to explain why the working tree is locked.
COMMANDS
add
 
 []

Create  and checkout  into it. The new working directory 
is linked to the current repository, sharing everything except working 
directory specific files such as HEAD, index, etc. As a 
convenience,  may be a bare "-", which is synonymous with @{-1}.

If  is a branch name (call it ) and is not found, and 
neither -b nor -B nor --detach are used, but there does exist a tracking 
branch in exactly one remote (call it ) with a matching name, treat 
as equivalent to:
$ git worktree add --track -b   /

If the branch exists in multiple remotes and one of them is named by 
the checkout.defaultRemote configuration variable, we’ll use that one for 
the purposes of disambiguation, even if the  isn’t unique across 
all remotes. Set it to e.g. checkout.defaultRemote=origin to always 
checkout remote branches from there if  is ambiguous but exists on 
the origin remote. See also checkout.defaultRemote in git-config[1] 
.

If  is omitted and neither -b nor -B nor --detach used, then, 
as a convenience, the new working tree is associated with a branch (call 
it ) named after $(basename ). If  doesn’t exist, a 
new branch based on HEAD is automatically created as if -b  was 
given. If  does exist, it will be checked out in the new working 
tree, if it’s not checked out anywhere else, otherwise the command will 
refuse to create the working tree (unless --force is used).

list

List details of each working tree. The main working tree is listed first, 
followed by each of the linked working trees. The output details include 
whether the working tree is bare, the revision currently checked out, the 
branch currently checked out (or "detached HEAD" if none), "locked" if the 
worktree is locked, "prunable" if the worktree can be pruned 
by prune command.

lock

If a working tree is on a portable device or 

[git-users] A more advanced git system with working trees per commit.

[skybuck2000]

Now this is something to my liking.

A git system where each commit and each branch has it's own working tree ?!

A tool which automates this would be great !

It should work as follows:

1. when a new branch is created create work tree for it in a sub folder
2. when a new commit is created or even before it a new folder is created.
3. commits should be split up in a pre-commit and post-commit.

the pre-commit states the programmers intention in the current working tree
the post-commit states the programmers work done.

4. each working tree/folder should automatically version if possible
version 0.01
version 0.02
version 0.03

5. the commit message should be recorded in the folder name above
version 0.01 post-commit message
version 0.02 post-commit message
version 0.03 pre-commit message

version 0.01-branch-feature-a
version 0.01-branch-feature-b

I know this system has limitations but it would integrate really well with 
my existing application development experience...

and it has then the best of both worlds.

Fast application development.
Redundancy
Build anything at any time
Run anything at any time.
Access to anything.
Can very quickly look back at older versions.
+
Git co-operation / team development.
Git distribution stuff
Git integrity checking maybe.

Git should and will evolve into something like this.

Better versioning information, more stability, more backwards 
compatibility, not one code for all, code for all times.

Let me know if such a system already exists.

Yes it may  not be suited for linux big 2 gigabyte kernel development, 
because of copies in working trees, but we are not all developing big 
kernels.

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/7e900dc9-69e5-4700-8d71-04f3bdd18b69n%40googlegroups.com.

[git-users] Re: GIT FUCKING SUCKS, ONE WORKING COPY IS NOT ENOUGH.

[skybuck2000]

NOW YOU UNDERSTAND WHY:

A more advanced git system with working trees per commit.

A more advanced git system with working trees per commit.

Now this is something to my liking.

A git system where each commit and each branch has it's own working tree ?!

A tool which automates this would be great !

It should work as follows:

1. when a new branch is created create work tree for it in a sub folder
2. when a new commit is created or even before it a new folder is created.
3. commits should be split up in a pre-commit and post-commit.

the pre-commit states the programmers intention in the current working tree
the post-commit states the programmers work done.

4. each working tree/folder should automatically version if possible
version 0.01
version 0.02
version 0.03

5. the commit message should be recorded in the folder name above
version 0.01 post-commit message
version 0.02 post-commit message
version 0.03 pre-commit message

version 0.01-branch-feature-a
version 0.01-branch-feature-b

I know this system has limitations but it would integrate really well with 
my existing application development experience...

and it has then the best of both worlds.

Fast application development.
Redundancy
Build anything at any time
Run anything at any time.
Access to anything.
Can very quickly look back at older versions.
+
Git co-operation / team development.
Git distribution stuff
Git integrity checking maybe.

Git should and will evolve into something like this.

Better versioning information, more stability, more backwards 
compatibility, not one code for all, code for all times.

Let me know if such a system already exists.

Yes it may  not be suited for linux big 2 gigabyte kernel development, 
because of copies in working trees, but we are not all developing big 
kernels.

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/5b89440a-e47e-43b2-9c7d-3182e9f16544n%40googlegroups.com.

[git-users] Re: git log --graph --all makes top line fall of screen.

[skybuck2000]

This may solve the white commit hash id problem:

https://stackoverflow.com/questions/11515089/why-no-yellow-in-powershell-and-posh-git

"
It turns out PowerShell's console renders System.ConsoleColor.DarkYellow as 
white:
[Enum]::GetValues([ConsoleColor]) | %{ Write-Host $_ -ForegroundColor $_ } 

Using bold yellow instead, which renders with System.ConsoleColor.Yellow, 
works:
git log --pretty='%C(bold yellow)%h%Creset %s' --abbrev-commit 
"

I will investigate this soon/probably tomorrow.

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/a87e01fb-7a2d-4fd4-926a-e32b4b8bea07n%40googlegroups.com.

[git-users] GIT: Split file into multiple files, then detect changes in updated original file and apply to multiple files.

[skybuck2000]

 GIT: Split file into multiple files, then detect changes in updated 
original file and apply to multiple files.

File Original contains:

ObjectA

Some funtions for Object A

some more functions for Object A

ObjectB

Some functions for Object B

some more functions for Object B

ObjectC

Some functions for Object C

some more functions for Object C


This should be split up into three files:

ObjectA

ObjectB

ObjectC


Such that File ObjectA contains:

ObjectA

Some funtions for Object A

some more functions for Object A


Such that File ObjectB contains:

ObjectB

Some funtions for Object B

some more functions for Object B


Such that File ObjectC contains:

ObjectC

Some funtions for Object C

some more functions for Object C


Later file Original is updated:

ObjectA

Some funtions for Object A

some more functions for Object A

even more functions for Object A

ObjectB

Some functions for Object B

some more functions for Object B

even more functions for Object B

ObjectC

Some functions for Object C

some more functions for Object C

even more functions for Object C


Is it somehow possible to use git to automate the updating of File ObjectA, 
File ObjectB File ObjectC so that all three files contain the new line such 
that:


Such that File ObjectA contains:

ObjectA

Some funtions for Object A

some more functions for Object A

even more functions for Object A


Such that File ObjectB contains:

ObjectB

Some funtions for Object B

some more functions for Object B

even more functions for Object B


Such that File ObjectC contains:

ObjectC

Some funtions for Object C

some more functions for Object C

even more functions for Object C


This is a scenerio where the original file is updated by a different user.

It would be very nice if a feature git had this detection capability for 
two reasons:

   1. 
   
   Big teams/projects that might not want to freeze such a big fle.
   2. 
   
   No-cooperating teams/repository that don't want to split the file.
   

Now that I understand git a little bit better, very maybe this will work:

What could be tried for the split dilemma, is the following idea:


1. The original document.txt is splitted in a "split commit" such that 
objecta.txt objectb.txt and objectc.txt exist.

2. This "split commit" can be isolated on top of original document.txt or 
anywhere basically.

3. Then when original document.txt is updated, try and reapply the "split 
commit", by basically re-basing it on top of the updated document.txt

So in git terms the idea is as follows:

BranchOriginalDocument   commit 1
document.txt
BranchSplittedDocument commit 2
objecta.txt
objectb.txt
objectc.txt
(could even be placed on their own sub branch if necessary because one 
branch might not be enough)
BranchUpdatedDocumentcommit 3
document.txt

now after after commit 3 is done, commit 2 could be rebased onto commit 3 
in the hopes that git will recgonize the split operation and maybe
repeat it on top of document.txt with updated contents.

the git command for this would like something like:

git rebase --onto BranchUpdatedDocument BranchOriginalDocument 
BranchSplittedDocument

tomorrow I will give this a try to see how far I get with this.

If it fails one more try would be to create additional branches or so, I 
saw somebody mention in the past that that might work.
not sure if they should be based on each other, but maybe... or seperate 
branches could be tried as well, all based on branch splitted document.

BranchSplittedDocument
BranchA
BranchB
BranchC  
BranchUpdatedDocument

(I am not sure if I have tried this before, maybe, but I understand git 
rebase a little bit better now, and git in general ! ;))

Any suggestions are welcome !

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/72239ec8-402a-4826-b277-b7d56b3c80aen%40googlegroups.com.

[git-users] Re: Removing origin/master from local repository after github master rename ?

[skybuck2000]

This website showed an interesting command, in the output git gives a hint 
how to remove a stale.

My first attempt failed, second attempt was successfull:

E:\SourceCode\PascalCoinGit\PascalCoin>git remote prune origin/master
fatal: 'origin/master' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

E:\SourceCode\PascalCoinGit\PascalCoin>git remote prune origin
Pruning origin
URL: https://github.com/SkybuckFlying/PascalCoin
 * [pruned] origin/master

E:\SourceCode\PascalCoinGit\PascalCoin>

Website:
https://stackoverflow.com/questions/9224754/how-to-remove-origin-from-git-repository

Command:
git remote show origin 

(Seen it before but completely forgot about it)

Result:
E:\SourceCode\PascalCoinGit\PascalCoin>git remote show origin
* remote origin
  Fetch URL: https://github.com/SkybuckFlying/PascalCoin
  Push  URL: https://github.com/SkybuckFlying/PascalCoin
  HEAD branch: PascalCoinMaster
  Remote branches:
GUIExperimentalBugFixes1   tracked
GUIExperimentalBugFixes2   tracked
GUIExperimentalBugFixes3   tracked
GUIExperimentalBugFixes4   tracked
GUIExperimentalBugFixes5   tracked
MergeTest  tracked
PIP-0026Windows7Implementation tracked
PascalCoinMaster   tracked
SkybuckMaster  tracked
TestPascalCoinMaster   tracked
refs/remotes/origin/master stale (use 'git remote prune' to remove)
  Local branches configured for 'git pull':
GUIExperimentalBugFixes1   merges with remote 
GUIExperimentalBugFixes1
GUIExperimentalBugFixes2   merges with remote 
GUIExperimentalBugFixes2
GUIExperimentalBugFixes4   merges with remote 
GUIExperimentalBugFixes4
GUIExperimentalBugFixes5   merges with remote 
GUIExperimentalBugFixes5
MergeTest  merges with remote MergeTest
PIP-0026Windows7Implementation merges with remote 
PIP-0026Windows7Implementation
SkybuckMaster  merges with remote SkybuckMaster
  Local refs configured for 'git push':
GUIExperimentalBugFixes1   pushes to GUIExperimentalBugFixes1   
(up to date)
GUIExperimentalBugFixes2   pushes to GUIExperimentalBugFixes2   
(up to date)
GUIExperimentalBugFixes3   pushes to GUIExperimentalBugFixes3   
(up to date)
GUIExperimentalBugFixes4   pushes to GUIExperimentalBugFixes4   
(up to date)
GUIExperimentalBugFixes5   pushes to GUIExperimentalBugFixes5   
(up to date)
MergeTest  pushes to MergeTest  
(up to date)
PIP-0026Windows7Implementation pushes to PIP-0026Windows7Implementation 
(fast-forwardable)
PascalCoinMaster   pushes to PascalCoinMaster   
(up to date)
SkybuckMaster  pushes to SkybuckMaster  
(up to date)
TestPascalCoinMaster   pushes to TestPascalCoinMaster   
(up to date)

E:\SourceCode\PascalCoinGit\PascalCoin>

git branch -r

Yup now it shows it's gone !

Case solved ! =D

Bye,
  Skybuck.
On Sunday, November 21, 2021 at 2:06:37 AM UTC+1 skybuck2000 wrote:

> Another one in here:
>
> E:\SourceCode\PascalCoinGit\PascalCoin\.git\logs\refs\remotes\origin
>
> I will try rename both to see what happens
>
> Now didn't help much, I renamed both to originalmaster and then branch -r 
> showed:
> origin/master
> origin/originalmaster
>
> So renamed them back to master... hmmm...
>
> Bye,
>   Skybuck.
> On Sunday, November 21, 2021 at 2:02:32 AM UTC+1 skybuck2000 wrote:
>
>> I tried moving this master file elsewhere it had some effect on the graph 
>> but even after moving
>> git branch -r
>> still shows it... 
>> so there is more to it...
>>
>> The hash pointed to some merge of remote/master into master
>>
>> and then there are some more commits like that.
>>
>> I will check other git files to see if I can find anything else.
>>
>> Bye,
>>   Skybuck.
>>
>> On Sunday, November 21, 2021 at 1:57:37 AM UTC+1 skybuck2000 wrote:
>>
>>> Also I see this file
>>>
>>> master
>>>
>>> in
>>>
>>> E:\SourceCode\PascalCoinGit\PascalCoin\.git\refs\remotes\origin
>>>
>>> Perhaps delete this file to get rid of it ? Is this safe ? :)
>>>
>>> There seems to be some hash inside of it.
>>>
>>> Bye,
>>>   Skybuck.
>>>
>>> On Sunday, November 21, 2021 at 1:55:41 AM UTC+1 skybuck2000 wrote:
>>>
>>>> Checking the hidden files of git, I find this, maybe this has something 
>>>> to do with it:
>>>>
>>>> packed-ref file:
>>

[git-users] Re: Removing origin/master from local repository after github master rename ?

[skybuck2000]

Also I see this file

master

in

E:\SourceCode\PascalCoinGit\PascalCoin\.git\refs\remotes\origin

Perhaps delete this file to get rid of it ? Is this safe ? :)

There seems to be some hash inside of it.

Bye,
  Skybuck.

On Sunday, November 21, 2021 at 1:55:41 AM UTC+1 skybuck2000 wrote:

> Checking the hidden files of git, I find this, maybe this has something to 
> do with it:
>
> packed-ref file:
>
> # pack-refs with: peeled fully-peeled sorted 
> 5dc3f5fb2342d306a029d7d4058fe28fd2daeee2 refs/remotes/origin/MergeTest
> 5a3a8b283ae8aa37272485fd9711b6d1e5ec33a8 refs/remotes/origin/master
> c33018784335daf4b47f622b88a76971855c refs/tags/1.5.6
> 262352cfb06842492d7e666cbd503f9b3b27578b refs/tags/2.0
> 68ac8ba519bf59541fc9009a0682abb8220cbba4 refs/tags/2.1.2
> 7980dfc903f716f493c28ba8d5ff323d6900fee4 refs/tags/2.1.3
>
> On Sunday, November 21, 2021 at 1:47:33 AM UTC+1 skybuck2000 wrote:
>
>> Just to be clear the local master branch was also renamed to 
>> SkybuckMaster.
>>
>> But origin/master still shows up ?
>>
>> Kinda strange ?
>>
>> Any explanation why this is  and if it can be completely removed ? 
>>
>> (Maybe destroying old commits might allow to do that, but if it's 
>> possible to do without destroying old commits that would be better ofcourse 
>> ;))
>>
>> I also tried
>> git fetch --prune
>>
>> But that did not help.
>>
>> git branch -r
>>
>> still shows origin/master
>>
>> to be present ?
>>
>> pushing or delete origin/master like so will give an error message kinda 
>> proving it's already gone ?
>>
>> git push origin --delete master
>> error: unable to delete 'master': remote ref does not exist
>>
>> git push origin --delete origin/master
>> error: unable to delete 'origin/master': remote ref does not exist
>>
>> git fetch origin
>>
>> git branch -r
>>
>> origin/master
>>
>> still shows up in bottom ?!
>>
>> Weird or what ?! =D
>>
>> Bye,
>>   Skybuck.
>> On Sunday, November 21, 2021 at 1:42:32 AM UTC+1 skybuck2000 wrote:
>>
>>> Hello,
>>>
>>> After renaming the github default branch "origin/master" to 
>>> "origin/SkybuckMaster" I notice that on the local repository there is still 
>>> some left over origin/master.
>>>
>>> When typing for example:
>>> git branch -a
>>> or 
>>> git branch -r
>>>
>>> It will still show origin/master
>>>
>>> Is this because in the past merges/commits and such where done onto this 
>>> remote branch ?
>>>
>>> Or is it possible to somehow remove origin/master from local repository.
>>>
>>> I may want to re-use origin/master in the future ?
>>>
>>> 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/7f8c26b8-973a-46a4-bba0-17cca99bc7ean%40googlegroups.com.

Re: [git-users] unable to push to github account

[skybuck2000]

Why does git for humans exists ?

How is it different from git for windows ?

Is git for humans for more general purposes questions ? or 
non-platform-related questions ?

(To original poster: seems like that exe or other services/exes that it 
uses needs that framework try installing it, if that don't solve it then 
new/different problem)

W11 comes with .net framework installed so then it should not be a problem.

Bye for now,
  Skybuck.

On Friday, November 12, 2021 at 12:59:45 PM UTC+1 Konstantin Khomoutov 
wrote:

> On Thu, Nov 11, 2021 at 06:53:05PM -0800, saheed ibrahim wrote:
>
> >i am getting this error report whenever i tried to push to github account
> >and i have downloaded the redistribution but unable to install 
> successfully.
> >how should i go about it to correct this error so that i can be able to
> >push my work to my github account
>
> Googling for the "git credential manage core" — that's what written in the
> title of the error message box from your screenshot, — brings in [1] which
> clearly hints on how to disable using of this feature completely, so I 
> would
> just do this.
>
> …and some assorted points while we're at it:
>
> * Please do not post images unless absolutely necessary: they are not 
> indexed
> by internet search engines, and as you can easily see looking at your own
> message, "unable to push to github account" has nothing to do with the real
> problem you're expeiencing so there are close to zero changes the next guy
> with the same problem will be able to find our exchange.
>
> Another aspect to this problem is that not everyone uses GUI- or web-based
> software to read mail; I, for one, use a terminal (text-mode) client,
> and viewing images in it requires a bit of extra effort; not too much,
> but sometimes some people will decide to just skip your message to not
> spend that effort.
>
> Any dialog box on Windows supports pressing Ctrl-C in it to copy the full
> text displayed there to the clipboard. Please use it.
>
> * This problem has nothing to do with Git itself; such questions are better
> asked on the mailing list dedicated to Git-for-Windows, [2].
>
> * "unable to install successfully" is not a problem statement because it is
> not actionable: the only thing which can be suggested after looking at it
> is "so there is some problem". Not too useful, right?
>
> So please, next time do spend more of your own time to spare the time of
> those who is supposed to help you with your problem.
>
> 1. https://github.com/microsoft/Git-Credential-Manager-Core#windows
> 2. https://groups.google.com/g/git-for-windows
>
>

-- 
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/729c2ff1-cbed-4fa0-9ff4-98611dfb686dn%40googlegroups.com.

[git-users] Re: Removing origin/master from local repository after github master rename ?

[skybuck2000]

I tried moving this master file elsewhere it had some effect on the graph 
but even after moving
git branch -r
still shows it... 
so there is more to it...

The hash pointed to some merge of remote/master into master

and then there are some more commits like that.

I will check other git files to see if I can find anything else.

Bye,
  Skybuck.

On Sunday, November 21, 2021 at 1:57:37 AM UTC+1 skybuck2000 wrote:

> Also I see this file
>
> master
>
> in
>
> E:\SourceCode\PascalCoinGit\PascalCoin\.git\refs\remotes\origin
>
> Perhaps delete this file to get rid of it ? Is this safe ? :)
>
> There seems to be some hash inside of it.
>
> Bye,
>   Skybuck.
>
> On Sunday, November 21, 2021 at 1:55:41 AM UTC+1 skybuck2000 wrote:
>
>> Checking the hidden files of git, I find this, maybe this has something 
>> to do with it:
>>
>> packed-ref file:
>>
>> # pack-refs with: peeled fully-peeled sorted 
>> 5dc3f5fb2342d306a029d7d4058fe28fd2daeee2 refs/remotes/origin/MergeTest
>> 5a3a8b283ae8aa37272485fd9711b6d1e5ec33a8 refs/remotes/origin/master
>> c33018784335daf4b47f622b88a76971855c refs/tags/1.5.6
>> 262352cfb06842492d7e666cbd503f9b3b27578b refs/tags/2.0
>> 68ac8ba519bf59541fc9009a0682abb8220cbba4 refs/tags/2.1.2
>> 7980dfc903f716f493c28ba8d5ff323d6900fee4 refs/tags/2.1.3
>>
>> On Sunday, November 21, 2021 at 1:47:33 AM UTC+1 skybuck2000 wrote:
>>
>>> Just to be clear the local master branch was also renamed to 
>>> SkybuckMaster.
>>>
>>> But origin/master still shows up ?
>>>
>>> Kinda strange ?
>>>
>>> Any explanation why this is  and if it can be completely removed ? 
>>>
>>> (Maybe destroying old commits might allow to do that, but if it's 
>>> possible to do without destroying old commits that would be better ofcourse 
>>> ;))
>>>
>>> I also tried
>>> git fetch --prune
>>>
>>> But that did not help.
>>>
>>> git branch -r
>>>
>>> still shows origin/master
>>>
>>> to be present ?
>>>
>>> pushing or delete origin/master like so will give an error message kinda 
>>> proving it's already gone ?
>>>
>>> git push origin --delete master
>>> error: unable to delete 'master': remote ref does not exist
>>>
>>> git push origin --delete origin/master
>>> error: unable to delete 'origin/master': remote ref does not exist
>>>
>>> git fetch origin
>>>
>>> git branch -r
>>>
>>> origin/master
>>>
>>> still shows up in bottom ?!
>>>
>>> Weird or what ?! =D
>>>
>>> Bye,
>>>   Skybuck.
>>> On Sunday, November 21, 2021 at 1:42:32 AM UTC+1 skybuck2000 wrote:
>>>
>>>> Hello,
>>>>
>>>> After renaming the github default branch "origin/master" to 
>>>> "origin/SkybuckMaster" I notice that on the local repository there is 
>>>> still 
>>>> some left over origin/master.
>>>>
>>>> When typing for example:
>>>> git branch -a
>>>> or 
>>>> git branch -r
>>>>
>>>> It will still show origin/master
>>>>
>>>> Is this because in the past merges/commits and such where done onto 
>>>> this remote branch ?
>>>>
>>>> Or is it possible to somehow remove origin/master from local repository.
>>>>
>>>> I may want to re-use origin/master in the future ?
>>>>
>>>> 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/f2b4d617-68e0-4696-a5bc-47bcdda9ca4bn%40googlegroups.com.

[git-users] Re: Removing origin/master from local repository after github master rename ?

[skybuck2000]

Another one in here:

E:\SourceCode\PascalCoinGit\PascalCoin\.git\logs\refs\remotes\origin

I will try rename both to see what happens

Now didn't help much, I renamed both to originalmaster and then branch -r 
showed:
origin/master
origin/originalmaster

So renamed them back to master... hmmm...

Bye,
  Skybuck.
On Sunday, November 21, 2021 at 2:02:32 AM UTC+1 skybuck2000 wrote:

> I tried moving this master file elsewhere it had some effect on the graph 
> but even after moving
> git branch -r
> still shows it... 
> so there is more to it...
>
> The hash pointed to some merge of remote/master into master
>
> and then there are some more commits like that.
>
> I will check other git files to see if I can find anything else.
>
> Bye,
>   Skybuck.
>
> On Sunday, November 21, 2021 at 1:57:37 AM UTC+1 skybuck2000 wrote:
>
>> Also I see this file
>>
>> master
>>
>> in
>>
>> E:\SourceCode\PascalCoinGit\PascalCoin\.git\refs\remotes\origin
>>
>> Perhaps delete this file to get rid of it ? Is this safe ? :)
>>
>> There seems to be some hash inside of it.
>>
>> Bye,
>>   Skybuck.
>>
>> On Sunday, November 21, 2021 at 1:55:41 AM UTC+1 skybuck2000 wrote:
>>
>>> Checking the hidden files of git, I find this, maybe this has something 
>>> to do with it:
>>>
>>> packed-ref file:
>>>
>>> # pack-refs with: peeled fully-peeled sorted 
>>> 5dc3f5fb2342d306a029d7d4058fe28fd2daeee2 refs/remotes/origin/MergeTest
>>> 5a3a8b283ae8aa37272485fd9711b6d1e5ec33a8 refs/remotes/origin/master
>>> c33018784335daf4b47f622b88a76971855c refs/tags/1.5.6
>>> 262352cfb06842492d7e666cbd503f9b3b27578b refs/tags/2.0
>>> 68ac8ba519bf59541fc9009a0682abb8220cbba4 refs/tags/2.1.2
>>> 7980dfc903f716f493c28ba8d5ff323d6900fee4 refs/tags/2.1.3
>>>
>>> On Sunday, November 21, 2021 at 1:47:33 AM UTC+1 skybuck2000 wrote:
>>>
>>>> Just to be clear the local master branch was also renamed to 
>>>> SkybuckMaster.
>>>>
>>>> But origin/master still shows up ?
>>>>
>>>> Kinda strange ?
>>>>
>>>> Any explanation why this is  and if it can be completely removed ? 
>>>>
>>>> (Maybe destroying old commits might allow to do that, but if it's 
>>>> possible to do without destroying old commits that would be better 
>>>> ofcourse 
>>>> ;))
>>>>
>>>> I also tried
>>>> git fetch --prune
>>>>
>>>> But that did not help.
>>>>
>>>> git branch -r
>>>>
>>>> still shows origin/master
>>>>
>>>> to be present ?
>>>>
>>>> pushing or delete origin/master like so will give an error message 
>>>> kinda proving it's already gone ?
>>>>
>>>> git push origin --delete master
>>>> error: unable to delete 'master': remote ref does not exist
>>>>
>>>> git push origin --delete origin/master
>>>> error: unable to delete 'origin/master': remote ref does not exist
>>>>
>>>> git fetch origin
>>>>
>>>> git branch -r
>>>>
>>>> origin/master
>>>>
>>>> still shows up in bottom ?!
>>>>
>>>> Weird or what ?! =D
>>>>
>>>> Bye,
>>>>   Skybuck.
>>>> On Sunday, November 21, 2021 at 1:42:32 AM UTC+1 skybuck2000 wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> After renaming the github default branch "origin/master" to 
>>>>> "origin/SkybuckMaster" I notice that on the local repository there is 
>>>>> still 
>>>>> some left over origin/master.
>>>>>
>>>>> When typing for example:
>>>>> git branch -a
>>>>> or 
>>>>> git branch -r
>>>>>
>>>>> It will still show origin/master
>>>>>
>>>>> Is this because in the past merges/commits and such where done onto 
>>>>> this remote branch ?
>>>>>
>>>>> Or is it possible to somehow remove origin/master from local 
>>>>> repository.
>>>>>
>>>>> I may want to re-use origin/master in the future ?
>>>>>
>>>>> 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/8da9ad71-9a65-4f4e-bf6e-c42b4b6116e5n%40googlegroups.com.

[git-users] Using * and - to scroll up and down ?

[skybuck2000]

This toshiba laptop L670 is starting to annoying me...

The page up/page down keys are all the way at the top of the keyboard above 
the numpad.

I constantly end-up pressing * and -  in an attempt to scroll.

It could be usefull to give git an option to use * and - for scroll up/down

when for example doing

git log --graph --all

Another possibility would be to ignore these key presses * and -

The annoying thing is after I press * and - but accident... git starts 
recording these... and it interrupts the scrolling... even if I press page 
up/page down that will no longer work and instead it will display at the 
bottom line:

--ESC[6~ESC[6~ESC[6~ESC[5~ESC[6~ESC[5~ESC[6~

This is in cmd.exe in git-bash.exe this annoying behaviour does not occur 
hmm...

I am evaluating which one I want to continue using cmd.exe or git-bash.

So far each one have their ups and downs.

cmd.exe has a more compact font, the colors are a little bit less 
cyberpunky... and there is no on-branch-indicator at the prompt.

I tried new git distro in windows 11 in vmware... but it strangely started 
mingw or something when I told it to use cmd.exe so that's strange... may 
have to set it up manually..

In windows 7 using cmd.exe with git.exe on path variable is actually quite 
nice to some degree.

Thing that annoys me in both is this:

git-bash:

E:

doesn't work.

cd E: 

does work

cmd.exe:

E:

does work

cd E: 

does not work. (just displays E: folder)

Exactly vice versa... also quite annoying.

I've started to prefer the cd E: method from bash kinda cool:
cd=change directory
or
cd=change drive

very cyberpunkish ! =D

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/ed54a06d-7bee-44af-b9b2-630f91961460n%40googlegroups.com.

[git-users] Re: Removing origin/master from local repository after github master rename ?

[skybuck2000]

Just to be clear the local master branch was also renamed to SkybuckMaster.

But origin/master still shows up ?

Kinda strange ?

Any explanation why this is  and if it can be completely removed ? 

(Maybe destroying old commits might allow to do that, but if it's possible 
to do without destroying old commits that would be better ofcourse ;))

I also tried
git fetch --prune

But that did not help.

git branch -r

still shows origin/master

to be present ?

pushing or delete origin/master like so will give an error message kinda 
proving it's already gone ?

git push origin --delete master
error: unable to delete 'master': remote ref does not exist

git push origin --delete origin/master
error: unable to delete 'origin/master': remote ref does not exist

git fetch origin

git branch -r

origin/master

still shows up in bottom ?!

Weird or what ?! =D

Bye,
  Skybuck.
On Sunday, November 21, 2021 at 1:42:32 AM UTC+1 skybuck2000 wrote:

> Hello,
>
> After renaming the github default branch "origin/master" to 
> "origin/SkybuckMaster" I notice that on the local repository there is still 
> some left over origin/master.
>
> When typing for example:
> git branch -a
> or 
> git branch -r
>
> It will still show origin/master
>
> Is this because in the past merges/commits and such where done onto this 
> remote branch ?
>
> Or is it possible to somehow remove origin/master from local repository.
>
> I may want to re-use origin/master in the future ?
>
> 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/69e20063-0e6d-4e35-9865-705ff9456ffen%40googlegroups.com.

[git-users] Re: unable to push to github account

[skybuck2000]

You might be in luck, I noticed this weird mingw stuff as well in windows 
11 where I installed a new version of git.

The version without any problem that I am using is:

git version 2.29.2.windows.2

For now I believe the problem might be the following:

1. The latest git installer does something weird and uses mingw to setup a 
cmd.exe or fakes it.
or
2. Some weird build where git.exe or other stuff uses mingw 

Then again I just noticed git-bash uses mingw anyway but it's in the window 
title bar... so I guess newer builds of git go to some default user 
folder... kinda annoying but now for some reason it's more severe or font 
change... not sure what changed here is what I see on this older version:

new@new-PC MINGW64 /
$

Very strange stuff.

Well now I see what it's doing... it's using the account name and pc name 
to make that stuff at the front.

Making that very short will work a bit easier.

Bye for now,
  Skybuck.

On Friday, November 12, 2021 at 3:53:05 AM UTC+1 saol...@gmail.com wrote:

> i am getting this error report whenever i tried to push to github account 
> and i have downloaded the redistribution but unable to install successfully.
> how should i go about it to correct this error so that i can be able to 
> push my work to my github account
>

-- 
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/15e57609-d7e5-4c13-86a2-588f845a6054n%40googlegroups.com.

[git-users] Synchrozining and versioning "linked files"/"dependencies" language neutral/independent

[skybuck2000]

Programming languages like C, Delphi, Python, Java, C#, C++ and others 
often have include and import and use clausules and such in their program 
files.

For example:
include "filea.h";
uses fileb;
import graphics;

These pieces of synthax describe how the files are linked together and how 
they dependent on each other.

Each compiler writer/language designer could write a small little 
tool/parser that GIT.exe could use to discover links/dependencies between 
files.

Even graphics and other file types could make use of this feature/idea.

This allows GIT to become aware of what could be considered a "dependency" 
map.

Such a dependency map, or "view of dependency" would allow certain desired 
features.

One very important one is including version numbers/information in files, 
which is currently completely lacking.

Problem example:
file.a includes/uses/imports/depends on file.b

There are now three scenerios:

scenerio 1: file.a is changed/updated
scenerio 2: file.b is changed/updated
scenerio 3: both are changed/updated

question/problem:
which version of file.a used which version of file.b ?

There are two ways to tackle this problem:

1. Either development environments are made aware of git and different
versions.

2. Or the version information gets exported from git and stored into the 
files
themselfes, either in the file system as a special field, or appended to 
the filename.

Examples of solution 2 are:

file.a.version.001
file.b.version.001
file.a.version.002
file.b.version.002

Now for a more complex example to illustrate better the requirements:

file.a uses file.b, file.c, file.d, file.e.

if any of the file.b to file.e is updated/versioned then so should file.a, 
even though file.a did not change the final behaviour of file.a may have 
changed through different behaviours in file.b to file.e which are used by 
file.a, therefore it is highly desireable that file.a also gets 
versioned/up a version+1 in case any of it's dependencies is also 
versioned/changed/up a version+1

Furthermore by constructing a "dependency map" it can be seen that A also 
depends on other files, therefore it may be desireable to update all of 
their versions as well, and sync them, especially if they are in the same 
folder, this can be a strong indicator that these files belong together and 
should have the same version number to describe them as a form of a 
package, library, module and such though more implicit perhaps.

This could be set as a rule, "versioning/sync-up" files in the same folder.

When a commit is done, all files on the dependency map get a new 
incremented synchronized version number, at least the files in the same 
folder.

Different options could be used to also allow individual versioning.

The second tool that would be necessary from compiler writers is a "change 
include/uses/import" tool or functionality.

Where the compiler/parser parses the files on the dependency map, then 
scans the files for the dependency links and replaces the existing links 
with the new filenames with their new version numbers.

Such that builds don't break and all files uses all other files properly 
such that they use the correct updated/incremented versioning number.

Such a tool could be called "Link.exe" or "LinkUp" or "LinkDependency.exe"

This would allow GIT two things:

1. Query files for links to other files.
2. Update links inside files to other files.

Basically this would allow GIT to do proper versioning numbering by for 
example appending version numbers to file names. To keep version numbers in 
sync across
related files in folders, to replace version numbers inside 
include/users/import statements.

This feature would be/could be more fine-grained then submodules, I have 
not yet used submodules, and could be weird to use submodules per file in 
some folder.

Plus for development environments it becomes more clear which version is 
actually used/opened.

Mixing of versions also becomes possible to some degree.

For example
file.a.002 could use file.b.001 and file.b.002

to transition between functionality or compare, or provide backwards 
compatibility and so forth.

also mixed-versions of file allows code to be upgraded more gradually 
instead of all or nothing.

For example some files could still use apiv1 while updated files could use 
apiv2 or libraryv2.

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/c5d30755-8288-490e-bc90-1200cdb61ac9n%40googlegroups.com.

[git-users] Integrating GIT with my own versioning system.

[skybuck2000]

My own versioning system is very simple and used for solo development 
99.9%.

I will give an example of how this works.

The main thing is "folders", "version number in folders" and "comments in 
folders".

For example, let's suppose I want to test an algorithm called "Jack".

I would create a folder like so:

C:\Source Code\Tests\Test Jack\version 0.01 original code\

Then I would make a copy of that code:

C:\Source Code\Tests\Test Jack\version 0.02 modify it\

Now I can start making save modifications.

Perhaps I will get an idea how to improve it with some new algorithmic 
parts:

C:\Source Code\Tests\Test Jack\version 0.03 and new algorithm to it\

Perhaps I then want to do an optimization sessions

C:\Source Code\Tests\Test Jack\version 0.04 optimize it\

Perhaps then I may want to restructure it:

C:\Source Code\Tests\Test Jack\version 0.05 restructure\

Then I discover/decide the re-structuring failed and I want to skip that 
version.

I rename it:

C:\Source Code\Tests\Test Jack\version 0.05 restructure (failed, skip this 
one)\

Then I want to finally clean up some code/comments for sharing with others 
or stablize it

C:\Source Code\Tests\Test Jack\version 0.06 based on version 0.04 clean up 
code\

Then perhaps I want to make some last small changes/adjustments settings 
for a release version.

C:\Source Code\Tests\Test Jack\version 0.07 release it\

Finally I might want to share/incoorporate it into a git release/commit.

This is where it gets a bit hairy. I could create a git init inside that 
release folder, but as soon as I copy that folder, it copies the whole git 
database, possibly leading to lost of wasted harddisk space and it doesn't 
make much sense.

Further more this copieing of folders has some benefits compared to git:
1. more redundancy.
2. quick access to different versions, code copieing possibilities.
3. easy to see sense of progression.
4. all files in a version belong together.
5. easy to make copies and make changes
6. any change is automatically saved without requiring any commits.
7. I can copy from any version without having to cancel any unstaged 
changes.
8. I can even work on multiple versions at the same time, example:

C:\Source Code\Tests\Test Jack\version 0.08a idea 1\ 
C:\Source Code\Tests\Test Jack\version 0.08b idea 2\
C:\Source Code\Tests\Test Jack\version 0.08c idea 3\

So for slight branching git does not really offer any benefit and this can 
be done fine with windows explorer and ntfs folder structures also 
incredibly fast.

However comparing versions and detecting differences might become a bit 
more complex, this is where git and other tools have some value.

I could even sub version those folders or any folder and make a sub version 
and move code around, example:

C:\Source Code\Tests\Test Jack\version 0.09\sub version 0.01 test something 
C:\Source Code\Tests\Test Jack\version 0.09\sub version 0.02 test different 
something
C:\Source Code\Tests\Test Jack\version 0.09\sub version 0.03 test alternate 
something

I could then select one or copy code from multiple sub versions to produce 
final new version

C:\Source Code\Tests\Test Jack\version 0.10 merged version mostly based on 
version 0.02\

So basically the possibilities are endless.

A second versioning system is also in place, versioning files themselfes in 
case I only want to change files and not folders, this gets a bit messy and 
can run out of sync but it can be convenient, example:

C:\Source Code\Tests\Test Jack\version 0.11\unit_main_version_011.pas 
C:\Source Code\Tests\Test Jack\version 0.11\unit_algo_version_011.pas 
C:\Source Code\Tests\Test Jack\version 0.11\unit_helper_version_011.pas 
C:\Source Code\Tests\Test Jack\version 0.11\unit_helper_version_012.pas
C:\Source Code\Tests\Test Jack\version 0.11\unit_helper_version_013.pas

This way I can quickly try out different helper versions without copieing 
the entire folder and without re-naming all versions in all these files.

version numbers in file names are not that usefull for application code, 
there are however very usefull for shared code between applications, so 
that applications can always be build against exact version numbers.

This is what worries me the most for GIT, it's not suited for shared files 
between applications, updating code in a "working folder" would be horrible 
and break every application that ever used it, here versioning in folder 
names and file names is far superior to always be able to build ANYTHING at 
ANYTIME.

No check outs needed, not digging into commit hashes, etc, it's almost 
funny to think how some people, git users or windows manage to do this at 
all, some might use some kind of version field inside 
binaries/executables/dlls, but that is after the dead, after everything is 
build, this may be for binary compatibility. What I wrote above is about 
source capability where everything is build into a single binary.

Anyway I hope to have convinced you somewhat that GIT is not ideal for 

[git-users] !!! RED ALERT: SHIELDS UP, TROJAN SOURCE HAS ARRIVED !!!

[skybuck2000]

I haven't even read this document fully yet, but all signs point to MAJOR 
TROUBLE AHEAD for open source projects:

https://www.trojansource.codes/trojan-source.pdf

My recommendation is to hold all patches/pull requests until 
solutions/defense/shields are found !

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/5a352c52-7f95-43a4-b779-1d63335bd2fan%40googlegroups.com.

[git-users] Re: Integrating GIT with my own versioning system.

[skybuck2000]

Finally I shall shem some light on that 0.01% that I actually worked 
together with other noobie programmers and have I incorporated it into my 
own version system and it kinda makes sense.

If I recall correctly it went something like:

version 0.10\Ralph
version 0.10\Krijn
version 0.10\Bart

Something like that and their code contributions would be seperated by the 
person's name.

That does kinda make sense because it is their work and their version of 
something.

It where individual parts and so forth or copies of something.

As long as people work on their own files that is ok. It could even done as 
follows:

some_file_version_10_ralph.pas.

This could even be used in a more complex situation where persons are 
editing each other files and the person's name that last edit it is stored 
in the filename.

At least this would give some idea who to "call" if something broke or who 
is responsible for last changes.

Downside is project files and other files would need to be aware of this 
and change accordinly or this information would need to be stored in some 
field of the underlieing file system and file but should also be somewhat 
visible.

This would give some more freedom to people creating their own versions of 
code, while at the same time using it and to check for bugs/errors and 
operation and efficiencies.

Without username seperation it would become hard and code would have 
constantly to be swapped out for that of somebody else, now a project can 
test/run all code at the same time.

Eventually once it's all good the names can be removed and presented as a 
total predict.

Right now GIT can be considered a bit dictatorish other go with the 
main fork or get lost ! LOL.

There is the possibility of forking, but which fork is more recent and more 
evolved ? Hard to tell without any versioning information. 

One possibility is to look at number of commits, for that the versioning 
system itself is necessary or github. This is somewhat less ideal.

Also without a "grand" versioning system/naming system there is the 
possibility of version conflicts in a more free system (where multiple 
users end up using the same versions for their own evolved versions...)

Bye for now,
  Skybuck.
On Sunday, October 31, 2021 at 7:31:54 AM UTC+1 skybuck2000 wrote:

> There remains one big problem with this idea.
>
> By using git all version information is basically lost and all the effort 
> I put into version folders and version files is lost and my users of my 
> fork would not benefit from versioning at all.
>
> For them it would be "all" or "nothing".
>
> Unless they start versioning their copies of the fork themselfes, this 
> could lead to "wild" grow of all kinds of different version numbers based 
> on their own copies.
>
> One possible solution is to add tags and release/version numbers, but 
> again lots of work, overhead and it doesn't version everything, only when a 
> tag is applied.
>
> I am a strong believer in that everything should be versioned at all times 
> and it should be crystal clear against what version is being coded, or what 
> version of a file/folder is included in a build...
>
> Hmmm...
>
> That would leave only one possibility:
>
> "upload all or most or desired" version folders.
>
> However GIT does not seem to like this much ?
>
> Is it possible to "instruct" GIT to do it's thing based on version folders 
> ? That would be somewhat cool !
>
> Bye,
>   Skybuck.
>
> On Sunday, October 31, 2021 at 6:14:40 AM UTC+1 skybuck2000 wrote:
>
>>
>> My own versioning system is very simple and used for solo development 
>> 99.9%.
>>
>> I will give an example of how this works.
>>
>> The main thing is "folders", "version number in folders" and "comments in 
>> folders".
>>
>> For example, let's suppose I want to test an algorithm called "Jack".
>>
>> I would create a folder like so:
>>
>> C:\Source Code\Tests\Test Jack\version 0.01 original code\
>>
>> Then I would make a copy of that code:
>>
>> C:\Source Code\Tests\Test Jack\version 0.02 modify it\
>>
>> Now I can start making save modifications.
>>
>> Perhaps I will get an idea how to improve it with some new algorithmic 
>> parts:
>>
>> C:\Source Code\Tests\Test Jack\version 0.03 and new algorithm to it\
>>
>> Perhaps I then want to do an optimization sessions
>>
>> C:\Source Code\Tests\Test Jack\version 0.04 optimize it\
>>
>> Perhaps then I may want to restructure it:
>>
>> C:\Source Code\Tests\Test Jack\version 0.05 restructure\
>>
>> Then I discover/decide the re-structuring failed and I want to 

[git-users] Re: Integrating GIT with my own versioning system.

[skybuck2000]

There remains one big problem with this idea.

By using git all version information is basically lost and all the effort I 
put into version folders and version files is lost and my users of my fork 
would not benefit from versioning at all.

For them it would be "all" or "nothing".

Unless they start versioning their copies of the fork themselfes, this 
could lead to "wild" grow of all kinds of different version numbers based 
on their own copies.

One possible solution is to add tags and release/version numbers, but again 
lots of work, overhead and it doesn't version everything, only when a tag 
is applied.

I am a strong believer in that everything should be versioned at all times 
and it should be crystal clear against what version is being coded, or what 
version of a file/folder is included in a build...

Hmmm...

That would leave only one possibility:

"upload all or most or desired" version folders.

However GIT does not seem to like this much ?

Is it possible to "instruct" GIT to do it's thing based on version folders 
? That would be somewhat cool !

Bye,
  Skybuck.

On Sunday, October 31, 2021 at 6:14:40 AM UTC+1 skybuck2000 wrote:

>
> My own versioning system is very simple and used for solo development 
> 99.9%.
>
> I will give an example of how this works.
>
> The main thing is "folders", "version number in folders" and "comments in 
> folders".
>
> For example, let's suppose I want to test an algorithm called "Jack".
>
> I would create a folder like so:
>
> C:\Source Code\Tests\Test Jack\version 0.01 original code\
>
> Then I would make a copy of that code:
>
> C:\Source Code\Tests\Test Jack\version 0.02 modify it\
>
> Now I can start making save modifications.
>
> Perhaps I will get an idea how to improve it with some new algorithmic 
> parts:
>
> C:\Source Code\Tests\Test Jack\version 0.03 and new algorithm to it\
>
> Perhaps I then want to do an optimization sessions
>
> C:\Source Code\Tests\Test Jack\version 0.04 optimize it\
>
> Perhaps then I may want to restructure it:
>
> C:\Source Code\Tests\Test Jack\version 0.05 restructure\
>
> Then I discover/decide the re-structuring failed and I want to skip that 
> version.
>
> I rename it:
>
> C:\Source Code\Tests\Test Jack\version 0.05 restructure (failed, skip this 
> one)\
>
> Then I want to finally clean up some code/comments for sharing with others 
> or stablize it
>
> C:\Source Code\Tests\Test Jack\version 0.06 based on version 0.04 clean up 
> code\
>
> Then perhaps I want to make some last small changes/adjustments settings 
> for a release version.
>
> C:\Source Code\Tests\Test Jack\version 0.07 release it\
>
> Finally I might want to share/incoorporate it into a git release/commit.
>
> This is where it gets a bit hairy. I could create a git init inside that 
> release folder, but as soon as I copy that folder, it copies the whole git 
> database, possibly leading to lost of wasted harddisk space and it doesn't 
> make much sense.
>
> Further more this copieing of folders has some benefits compared to git:
> 1. more redundancy.
> 2. quick access to different versions, code copieing possibilities.
> 3. easy to see sense of progression.
> 4. all files in a version belong together.
> 5. easy to make copies and make changes
> 6. any change is automatically saved without requiring any commits.
> 7. I can copy from any version without having to cancel any unstaged 
> changes.
> 8. I can even work on multiple versions at the same time, example:
>
> C:\Source Code\Tests\Test Jack\version 0.08a idea 1\ 
> C:\Source Code\Tests\Test Jack\version 0.08b idea 2\
> C:\Source Code\Tests\Test Jack\version 0.08c idea 3\
>
> So for slight branching git does not really offer any benefit and this can 
> be done fine with windows explorer and ntfs folder structures also 
> incredibly fast.
>
> However comparing versions and detecting differences might become a bit 
> more complex, this is where git and other tools have some value.
>
> I could even sub version those folders or any folder and make a sub 
> version and move code around, example:
>
> C:\Source Code\Tests\Test Jack\version 0.09\sub version 0.01 test 
> something 
> C:\Source Code\Tests\Test Jack\version 0.09\sub version 0.02 test 
> different something
> C:\Source Code\Tests\Test Jack\version 0.09\sub version 0.03 test 
> alternate something
>
> I could then select one or copy code from multiple sub versions to produce 
> final new version
>
> C:\Source Code\Tests\Test Jack\version 0.10 merged version mostly based on 
> version 0.02\
>
> So basically the possibilities are endless.
>
> A second vers

Re: [git-users] Integrating GIT with my own versioning system.

[skybuck2000]

On Sunday, October 31, 2021 at 2:27:29 PM UTC+1 o...@ucm.es wrote:

> I have to admit, I am a bit lost in your description. A couple of remarks, 
> though. 
>

I thought it was simple enough but ok, I will try and give a procedural 
description and some further explanations.

The procedural for me coding is as follows:

1. I wake up.
2. I used to start my (Dream)PC, though lately I keep it down cause it 
doesn't feel well lol.
3. I go to the project I want to work one.
4. The very first thing I do is I make a copy of the latest version folder 
with windows explorer.

So I go to:
"C:\Source Code\My Super Duper Trooper Application\version 1.15"
I click it, I just copy and then I pasted it:
"C:\Source Code\My Super Duper Trooper Application\version 1.15 copie"

5. Then I rename it with a description of what I want to do/accomplish that 
today.

Note how there are a couple of things different about this compared to GIT:

Let me first explain why this workflow once again:
5.1 The main thing is ALWAYS making a copy before I start to work on 
anything because of two main reasons:
5.1.1 I don't want to loose any code of the previous day, always making a 
COPY before any new work assures I never loose work.
5.1.2 I don't know how I am feeling this day... maybe my brain is all 
screwed up and I do something stupid, it's rare but it might happen ! =D
5.1.3 I takes away any fear I have about editing code. I can do whatever I 
want, if I screw up I don't loose anything, except what I did today.
5.1.4 and if I did do something usefull today I can simply make another 
copy and safe my progress that way forever/safely.
5.1.5 I basically never delete any versions whatsoever unless it's total 
garbage and I really don't want to confuse myself in the future.

Now try and notice a couple of things different from GIT:
5.2 I always get a clean COPY, I always SAVE my progression NO MATTER WHAT. 
This is different from GIT, where COMMITS are not always possible because 
of a whole bunch of reasons, this is dangerous (risk of losing work) and 
this can be annoying and might even lead to stupid commands to get GIT to 
move on.
5.3 Another big difference is my "commit" message which is incorporates 
into the folder name. I write at the START of the day what it is that I 
wanted to do, not at the END of the day.
With GIT commit I can only write a commit message at the end of the day, 
BUT ONLY if I can do a successull COMMIT, this is dangerous because if I 
can't do a COMMIT I might loose information, I might forget what I wanted 
to do that day with that particular copy/version. One way around this would 
be to give the branch a longer name. However folder names allow longer 
names/descriptions, too long branch names might get a bit annoying.

^ These are two valid slight complains against GIT, I hope this is taking a 
bit more seriously but ok.

Anyway so in short my workflow is:

1. WAKE UP
2. SELECT PROJECT/FOLDER
3. COPY & PASTE PROJECT/FOLDER
4. INCREMENT PROJECT/FOLDER VERSION
5. DESCRIBE INTENDED WORK IN PROJECT/FOLDER VERSION.

^ This workflow is repeated every day, logs my progressions, keeps any of 
my work safe. 

1. I would never ever have space in directory names. That is calling 
> for trouble, but if it works for you fine. 
>

I feel the opposite, spaces are very important to be able to type relaxed 
and make good messages. typing underscores can lead to mussle strain 
because of weird shift key usage and such, typos and other mischief, though 
sometimes I do avoid spaces in names and revert to capitals, but rarely 
underscores _.
 

> 2. I used a similar approach, quite a long a time ago, before I 
> switched to RCS, then (forced) to CVS and then to git/hg. The 
> problem of this approach is: there is no equivalent to 
>
> git log --graphical or friends


This command does not work, is this pseudo code for a command ? I am a bit 
intrigued about the friends thing ? :)
 

> so you are completely on loss about the logical dependence of 
> your «commits» if I can call them commits. 
>

On the contrary, every version is simply build on the previous version 
number except if otherwise stated.
version 0.09
version 0.10

^ version 0.10 logically follows version 0.09 that is the whole idea of 
versioning as far as I am concerned :)

If you mean library dependence that is handled via project file and paths 
to folders/files.

3. It seems that you dislike hashes, (what I can understand to a 

certain extend from the usability point of view, at least for a 
> single user), but you can 
>

If GIT breaks down or is removed no hashes available what so ever. I like 
recording versioning information into the files themselfes.
 

> a. Either use 
> git log --graph --decorate --pretty=short | git name-rev --stdin | more 
>

Strangely the pipe command | more does not work in this combination but 
without it it did work.

It seems to "auto-tag" everything.
 

> b. Or switch to mercurial which has a local number system,


I have heard 

Re: [git-users] Integrating GIT with my own versioning system.

[skybuck2000]

the Git repo built. At least it gives a better overview, though the 
> diffs can be terrible. 
>

Why were the diffs terribles to many code changes all at once ?

Git is especially good in collaborative work, without some top knob 
> being in 'control'. The hash is simple and unique and avoids all the 
> coordination issues. 
>

This is a good point you make while not 100% theoretically correct there is 
a small chance of hash conflict, but in principle I can see how each hash 
in the world might be unique ?! ;)

Though one could consider this a matter of principle, do I really want to 
base collaborative work based on "luck" getting a unique hash by luck ? 
hmmm...

What could be the risk of basing it on a hash conflict ? Hmmm has this ever 
happend to the Linux Kernel :) ?! =D
 

> > version numbers in file names are not that usefull for application 
> code, there are however very usefull for shared code between 
> applications, so that applications can always be build against exact 
> version numbers. 
>
> > This is what worries me the most for GIT, it's not suited for shared 
> files between applications, updating code in a "working folder" would be 
> horrible and break every application that ever used it, here versioning 
> in folder names and file names is far superior to always be able to 
> build ANYTHING at ANYTIME. 
>
> This is a 'mental model' misunderstanding. It is a 'kit of parts / parts 
> catalog' viewpoint (home built vehicle), while Git's primary view is 
> that of 'the project' (compare to having a make/model of a car). 
>

Isn't this the same thing, software is build up out of modules=parts.
 

> In Git you would designate each of the resuable folder/files as a 
> sub-module, which can then be integrated when/wherever it's needed by a 
> major project. The (supra-)project choses the version that is used.


OK, point taken, so you are "saying" shared libraries and such should have 
a submodule.
This is where it gets a bit hairy, this kinda implies and means GIT has to 
be "applied" to libraries that I may not want to work on at all, libraries 
from other people.
But I still have to GIT-ti-FY them.

Now one could argue, wait a moment Skybuck, if you don't work on them then 
you don't have to GIT-ti-FU them but here lies a bit of the danger... In 
the future I might discover a bug or problem or a desire to modify a 
library and then BAM/BINGO... now this introduces a BIG problem, because so 
far, let's suppose version information was missing in GIT then GIT at this 
point has no idea of what library was being used. So to solve this problem 
I would have to add a SUB MODULE before making any changes to the library 
and then it becomes QUESTIONABLE if previous GIT commits can understand 
what SUBMODULE/hash was supposed to be used ? Consider this a serious 
question:

What happens to previous commits if a SUBMODULE is later introduced ? Here 
it gets very fuzy.

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/210ad64a-783e-4a64-a6dd-a88b5f73f6dfn%40googlegroups.com.

Re: [git-users] Integrating GIT with my own versioning system.

[skybuck2000]

>
> I bet Git 
> feels like one of those taxi rides through an unfamiliar city.. 
>

The GIT bash feels a bit cyber-punk-ish =D

It feels very cool, though there are plenty of git bash/text/gui bugs and 
flickers and issues as well as the editor.

I particularly like the 
git log --graph --all 
command

Very cyber-punk-ish.

And I also like the ANSI coloring... also very cyber-punk-ish ! =D

The greens, the pinks, the cyans. Remembers me of GOOD TIMES, the dial-up 
modem, BBS times ! =D

And a little bit Star Trek Online chat windows ! ;)
 

>
> > So far I have used GIT mostly with git commands, I know there is a GUI 
> > but then I feel more disconnected, for now it makes more sense to work 
> > like I was working in ms-dos to get more a feel for it. 
>
> I would recommend trying at least the git-gui and gitk at least for 
> their alternate view points when exploring Git. 
>

On the other hands the GIT guis feels a bit child-esh, amaturistic, 
clumsie, slightly ugly, slightly to compacted but this could be to display 
more.

Maybe my oppion about this will change, I may try GUI at a later stage, for 
now I kinda like the git bash commands too much, I can take it slow that 
way and have to think carefully what I am doing.

With the GIT GUI I worry a bit too much that I start "clicking" on 
everyting like a raving lunatic and accidentally issue all commands of 
hidden/secret commands behind those GUI buttons.

I don't really know at this point what the GUI does/buttons/commands kinda 
hard to tell, so that is a bit of guess work/gamble work... with commands 
at least I kinda know exactly what I am getting if I read the manual... 
sometimes I gamble a bit with commands as well, if I forgot actually how it 
worked... so far git is somewhat robust against gambling commands =D
Maybe my luck will run out some time =D or perhaps slowly the commands will 
in-grain itself into my brain and get stuck there ! ;)

There are plenty of times when I forget to put GIT in front of it for 
example so it remains a bit of a risk.
  

> Because the basic data model of Git hasn't changed and is rock solid all 
> the gui's essentially show the same stuff at different levels of 
> prettiness and soft rounded graphics. Git-gui and gitk are TCL apps 
> which are multi-OS. 
>

This may be one of the main reasons why I don't like the look of the GIT 
gui, it does look like a TCL app, it doesn't look like a genuine native 
windows app.
If something breaks in TCL or TCL is incompatible on windows version X this 
GUI may stop working.
And then it becomes a question how good are those guys at keeping it 
cross-platform/keeping it working.
I am not sure how trust worthy and high quality TCL is.

However Visual Studio or Delphi code should be much harder to break. I can 
vouch for Delphi based GUIs, Visual Studio a lot less.

TCL I don't know ? What technology is it based on ? Probably some visual 
studio code ?
 
Does this TCL GUI work on Windows 95, Windows 98, Windows XP, Windows NT, 
Windows Vista, Windows 7, Windows 10, Windows 11 ???

I bet it probably doesn't work on all versions and somewhere it will 
probably crash and I really don't want to run into those kinds of issues.
There will probably be some missing DLL or it's probably linked against 
some newer Windows DLL version, this may be a consequence of using the 
Visual Studio or Delphi compiler, so this is a complaint against these 
compilers, However if the correct compiler is used for the correct windows 
version then multiple TCL GUIs can be produced for each operating system.
Or TCL gui has to dynamically load DLLs and use some special compiler 
technology.

Creating a fully cross-platform GUI is not as easy as it sounds. I do 
believe TCL may have put some work into it, but still... I would need to 
see some hard core evidence that it runs truely on all systems, all windows 
versions.

With ms-dos/text based BASH it's much less likely to break, perhaps this is 
a wrong assessment of me or it may be spot on, I am not sure what 
technology is used to display BASH text prompt and such, it's probably not 
CMD.exe based but it might be. CMD.EXE iswholy in windows. Microsoft 
depends on it to build windows, it's probably one of the last things to 
EVER break ! HAHA.

> 1. Big Open Soure Linux Operating System, here making simple copies 
> would fill up harddisks very quickly, so I can understand only storing 
> "differences". 
>

> This is one of the BIG LIES we tell.


I see a trend here. I also lied a bit, normally I don't lie... I do care 
about the ammount of storage space it takes, but again as long as it's not 
too much it's ok, then I don't care so half-a-lie.
 

> Git stores snapshots. It will


I may have noticed this. I did notice the GIT database can get quite large. 
One example is PascalCoin... it's git database seems to be 100 MB... it 
shouldn't be that big I think, I don't think the sources are that big, so 
this may be because of copies of all different 

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

[skybuck2000]

It would be usefull if there was a command to see the tracking information 
for the current branch, if any.

Right now I am trying to figure out if any tracking is set for the local 
branch to some kind of remote branch.

There does not seem to be a command for it ?

I know there are other commands to display all: git branch -vv

However if the number of branches become very large, I may end up having to 
search through such a list.

Displaying such a huge list also distracts from the rest of the git command 
flow.

So something more tiny would be appreciated.

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/4e765561-a3bb-4007-86ad-ecc58ce2a9a9n%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.

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 <https://gist.github.com/tfnico/4441562>. 
>

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.

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

Failed:

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git config --global commit.template 
C:\Tools\Git\CustomUserSettings\.gitmessage

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git commit
fatal: could not read 'C:ToolsGitCustomUserSettings.gitmessage': No such 
file or directory

Maybe a slash issue...

I'm starting to wonder if maybe this laptop has something to do with these 
lamps failures or perhaps neighbours... very strange...

So ya see the environment is already working against me ! LOL.

BIZAR !

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/50761f35-aa8d-45a3-b225-c7412aa6b99en%40googlegroups.com.

[git-users] Re: Somehow git stash lost my changes.

[skybuck2000]

One more thing:

Assuming git stash worked the way I thought it would work I was wondering 
what would happen if a re-base a "stashed" branch.

Well I guess we'll never know that answer for now =D

My hope ofcourse would be that it moves with it... 

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/b4b7acfc-37df-4dfb-a6f0-6d6d613c6353n%40googlegroups.com.

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

On Monday, December 6, 2021 at 9:34:52 AM UTC+1 Konstantin Khomoutov wrote:

> On Sun, Dec 05, 2021 at 09:03:53AM -0800, Philip Oakley wrote: 
>
> > Set up different 'username' on the two machines (or committer / author 
> > difference, etc). 
>
> [...] 
>
> ...also do not forget that it's OK to insert into a commit message any 
> number 
> of "machine-readable" fields such as 
>
> Machine: whatever-machine 
>
> Just make sure such stuff is placed after the initial (terse) message 
> and a blank line. Usually such key/value parts go last so that the whole 
> message looks like 
>
> A terse commit message 
>
> An long explanatory 
> commit message. 
>
> Keyword1: Value1 
> Keyword2: Value2 
>
> Such K/V options can then be parsed when needed. 
>
> Note that you can make Git use custom template for your commit message 
> with a 
> pre-created keyword through the "commit.template" configuration option. 
>
>
I assume the git operations below are kept ? this is not explained properly 
in following tutorial:

Create A Custom Git Commit Template | by Alex Wasik | Medium 


git config --global commit.template ~/.gitmessage

Also what is ment with ~/. ? Where is this folder located ? At root of any 
repository ?

So this would allow me to setup a gitmessage per repository ?

Or is this folder located somewhere in git distribution ?

If it's per repositoy then this is again not proper, and faulty. It says 
global.

So now more guess work for me.

I would like to setup git commit message such that:

1. It's true global no matter what repository I use.
2. I would like to keep this gitmessage with the mintty or git thing I am 
using.

I see a danger here though, if I switch to a different version I may loose 
this functionality and might not notice it after a while but ok.

3. I do not want to loose standard text such as:

Oh I can't even display it anymore, I was afraid of this, didn't want to 
set it yet, but finally decided to give it a try, but it did clearify 
something:
$ git commit
fatal: could not read 'C:/Users/Skybuck/.gitmessage': No such file or 
directory

So a shocking discovery is made, if this setting is wrong, git completely 
breaks, some might like it, some might not... not very robust is it this 
git, but at least it's clear that something is screwed up...

It's also surprising that git seems ~/. as that user folder... quite 
strange and very insenstive of git... I am not even working on C:  I have 
been working on E: all this time... at least mostly ! ;) ok git was 
installed on C: but so what... the os is there... but so what... I don't 
like it in general if apps integrate them selfes with some whacky operating 
system.

If git had chosen it's installation directory as it's home directory I 
would have been perfectly fine with that but I 100% dislike window user 
folders it sucks ass lot's of junk in there... easy to get stuff lost 
in there.

Also easy to forget that anything was stored in there of importance.  For 
that reason I don't like this solution.

I will try and give it a more absolute path and see if that works:

I'm thinking of something along the lines of :

C:\Tools\Git\CommitMessage\

or maybe
C:\Tools\Git\CustomUserSettings\CommitMessage

Yeah that last one gonna be the one.

Now first I try and reset this so I can show what I ment with other 
standard messages:

I tried to reset with:

$ git config --global commit.template 

Didn't work ofcourse shows current wrong setting.

then I tried:
$ git config --global commit.template ""

That didn't work either which again is kinda shocking ?!

How do I get rid of this faulty setting ? see below:

git config --global --unset commit.template

I would like to keep this below my own template:

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch AddThreadInfo
# Changes to be committed:
#   new file:   src/gui-classic/Frames/UFrameThreadInfo.dfm
#   new file:   src/gui-classic/Frames/UFrameThreadInfo.pas
#

Anyway I am getting a lot of copy & paste failures caused by two things:

1. Buggy left mouse
2. Sometimes git bash malfunctions and does not paste the new copied text, 
this is a very dangerous thing. I ended up pasting an entire log from git 
stash thread/message... I was lucky there... git bash is buggy and should 
be fixed or some save guards build in...

Especially reacting to enter commands, new lines and such, git bash should 
make it impossible to execute commands that were pasted... as a safety 
precaution... an option added to git bash to prevent accidental execution 
of commands would highly be appreciated, perhaps such an option already 
exists ?!?

Anyway I will give my path suggestion above a try and report on it later.

Also why the pattern:

Key:Value

is
Key=Value

also possible ?

Or anything else ?

Or is there some standard 

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

This is less easy then it seemed, I decided to remove the environment line 
just to save one line... but somehow the new lines are showing up as ^M... 
in vim(?) that kinda annoying:

^M
^M
Operating System: Windows 7 Home Edition^M
Virtualization Layer: VMWare Workstation 15^M
Virtual Operating System: Windows 11 Workstation Pro^M
Computer: Toshiba Laptop L670^M

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch AddThreadInfo
# Changes to be committed:
#   new file:   src/gui-classic/Frames/UFrameThreadInfo.dfm
#   new file:   src/gui-classic/Frames/UFrameThreadInfo.pas
#

^ At least these interesting lines are still displayed, rarely read them, 
though sometimes...
just good to know that git is functioning.

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/9e42bc94-1cc1-4eb5-85f3-61f11dcb1352n%40googlegroups.com.

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

I will give this a try, I hope it doesn't mess up other things, weird:

git config --global core.autocrlf true

I guess the problem was that the file is coming from windows ? But so what 
? vim can store any character in it it wants but apperently it stores 
windows characters in it on save and then later complains about it ?! Super 
weird and somewhat inconsistent but ok... I guess it's being nice because 
it notices that it's getting saved to windows ? Or something else is going 
on, bizar moments right now, let's see what happens:

git config --global core.autocrlf true

HAHAHAHA LOL didn't solve a god damn thing, problem remains.

I will try vim one more try.

Still same problem with ^M.

I give up for now... see you !

In this case giving up is good because the number of TABS required in 
FIREFOX to find the cause of this problem is going to be HUGE and crash my 
virtual machines LOL because I am trying to find a cure for one little 
fucking SPACE/NEWLINE NO THANK YOU BYE.

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/d4b2ce5f-5231-4dee-b6ee-d2430c56345an%40googlegroups.com.

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

First I set this back to default which is false according to stack overfow.

Would be nice if git has a restore setting to default option or something, 
cause if stackoverflow is wrong I am screwed, don't like relieing on 
history/stackoverflow... git could have changed after many years... kinda 
sucks I dont know for sure what the real default setting was, but here goes:

 git config --global core.autocrlf false

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/3369a78d-5524-41dd-8864-29765fbafcc4n%40googlegroups.com.

[git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

Two reasons:

1. For fun
2. In case anything goes wrong, in case it's caused by machine differences.
3. In case I want to know on what machine the git commit was done in case I 
need to go back to that repository, in case other repositories on other 
machines went wrong somehow and in case that repository is still intact. 

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/d28f9e0b-b1f6-4120-99a6-7429fb91f6ccn%40googlegroups.com.

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

>
> Will this be parseable by the tools you mentioned:


Machine:Windows 11 Workstation Pro

Or will spaces in the value cause problems ?

and should it be made:

Machine:"Windows 11 Workstation Pro" ?

Perhaps a comment should be added in front ?

# Machine: "Windows 11 Workstation Pro" but I guess then it would be 
ignored and not stored in the commit ?

So all the # that git shows is just for me during the commit and nothing  
happens with it ?

I was thinking... maybe these are "secret/hidden" instructions to 
instruction git what to do ? ;) =D

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/3787c7c7-ef35-4392-8ebc-5a5931d023fan%40googlegroups.com.

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

Then again, those lamps were old if I recall correctly, perhaps there was 
only one lamp still burning...

I replaced one big lamp on top left side, two lamps in there they going 
strong.

Other big lamp on top right side... also two lamps in it... one probably 
died a while ago.. and maybe tonight the other one died...

So maybe not neighbours fault... so now I cooled down a bit lol... and 
lolling about it hahahaha.

I need hard-core evidence that neighbours damaged it... can't call/blame 
people out on it without knowing 100% sure... so for now I will dismiss 
this as "Philips company screwing my over by making 
planned-obselence-lamps" that die after 10.000 hours of usage.

Bunch of fucking bastards, arg...

Did you know there is a lamp on the internet,being filmed and burning for 
30 years... yes it's possible to make lamps that last a very very very very 
very long time.

And now with this global pandemic... people might start running out of 
lamps because of transportation sector fails... 

Now do you see how bad this planned obselence is... it's a bloody fucking 
risk and assumes transports will be available...
Well USA is finding out the hard way right now what the mother of all fuck 
ups is !

Bye for now,
  Skybuck =D

-- 
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/da8189a8-87be-4c02-96ee-4767fee2b967n%40googlegroups.com.

[git-users] Re: Somehow git stash lost my changes.

[skybuck2000]

This is the first time I tried to do multi git stashes and it went horribly 
wrong because I did not understand how git stash works in this case.

My assumption and hope was that the "stash" was stored per branch.

So when I would switch back to the branch where the "stash" was stored and 
I would do a "pop" it would come back.

But instead it popped the wrong stash from another branch.

That is what I think happened so far, after that it gets vague... I 
probably did another git stash trying to push it back or something.

That is the part were it gets fuzy... since I pushed it back and such how 
were the changes lost ?

Anyway I am tired of this stash confusion, I don't like how this 
functionality is implemented currently.

Maybe later I will like it better.

I did read up on git stash, apperently stashes can be applied to different 
branches.

This is not the intended functionality that I had in mind when doing 
this... just wanted to store my changes on that branch AddThreadInfo and 
now they were horribly lost.

An improvement to git would be to automatically add the branch name where 
the stash occured...

I would like it better if stash would work the way I described, a "stack" 
per branch"... but ok... maybe in the future I might not like this

Right now I don't see the point in having a stack that works across 
branches, this has huge potential for confusion.

If I want to apply changes from other branches then there is git merge and 
such...

Perhaps git merge could be extended to merge stashes changes on branches... 
that would make more sense to me.

I am not amuzed,
 
Bye,
  Skybuck =D

-- 
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/b26c1993-c40f-4803-8dcf-6bb36063049cn%40googlegroups.com.

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

I would like to add something like this:

Environment:
Operating System: Windows 7 Home Edition
Virtualization Layer: VMWare Workstation 15
Virtual Operating System: Windows 11 Workstation Pro
Computer: Toshiba Laptop L670

This will help me remember in what environment I made these software 
changes, especially if in a far further I go do something else and forget 
about this.

I see some downsides to this:

1. The first line might cause problems.
2. Hackers get wiser.
3. My "teammates" might not like it if I add this data to the commits.
4. Increases size of git log/git commit messages, waste some screen space 
and some disk space.

WOW two lamps just failed at the same time ?! What are the odds of that... 
very weird... G4/G5 radiation ? Super strange... 

Anyway I was going to write, point 4 is a big concern when wanting to read 
git commit messages. I could try and reduce it to one line maybe.

If there was an option to hide this from standard git commit messages that 
be great if this could only be displayed if I really wanted to know this in 
case of some kind of confusion/emergency or issue.

I will assume this is not possible, but let me know if it is possible 
somehow... perhaps some "collapse" statement that git can process like:

{
Environment:
Operating System: Windows 7 Home Edition
Virtualization Layer: VMWare Workstation 15
Virtual Operating System: Windows 11 Workstation Pro
Computer: Toshiba Laptop L670
}

That would be cool and then I could write:

git log --graph --all --expand

I will give this git template a quick try but I will probably undo it soon, 
because git log spam is probably a bad idea.

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/25129b15-fc28-4153-a730-0069828b717bn%40googlegroups.com.

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

Concerning the broken lamps, my best hypothesis is the upstair neighbours 
banging the floor/ceiling to hard causing these lamps to fail again or 
maybe there is a slight short somewhere, but it's most likely the upstair 
neighbours I was a bit pissed the last few days, the banging the ceiling a 
bit hard recently... only 1 or 2 hours, but still way to loud.

I am definetly phoning them up tomorrow, gonna yell at them a little bit 
and let them know I am pissed, I have better things to do then replace 
lamps  and I could fucking break my neck or back replacing those fuckers... 
so now I am truely pissed and now they gonna get it via the phone ! no 
matter if nice people or not... when people break my shit I get angry ! ;) 
=D

Bye for now,
  Skybuck =D

-- 
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/8beea858-3f50-416f-b9f7-af5906bafdf4n%40googlegroups.com.

[git-users] Somehow git stash lost my changes.

[skybuck2000]

Here is the log of today, I remove the git log --graph --all to keep it 
shorter:

The file changes you see below are lost, how did this exactly happen ?

(I can guess but I would rather have an expert look at it):

(I don't like git stash much, maybe it should be called git stash push, 
just to make clear what it does,  what does git stash do ? is it like git 
stash push ? what is it's default behaviour?)

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(RefactorCode)
$ git switch AddThreadInfo
Switched to branch 'AddThreadInfo'
M   src/core/ULog.pas
M   src/core/UNetProtocol.pas
M   src/core/UNode.pas
M   src/core/UPCAbstractMem.pas
M   src/core/UPCOperationsBlockValidator.pas
M   src/core/UPCOperationsSignatureValidator.pas
M   src/core/UPoolMinerThreads.pas
M   src/core/UPoolMining.pas
M   src/core/URPC.pas
M   src/core/UTCPIP.pas
M   src/core/UThread.pas
M   src/gui-classic/UFRMAccountSelect.pas
M   src/gui-classic/UFRMDiagnosticTool.pas
M   src/gui-classic/UFRMRandomOperations.pas
M   src/gui-classic/UFRMWallet.dfm
M   src/gui-classic/UFRMWallet.pas
M   src/gui-classic/UFRMWalletConfig.dfm
M   src/gui-classic/UGridUtils.pas
M   src/pascalcoin_wallet_classic.dpr
M   src/pascalcoin_wallet_classic.dproj

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git stash
Saved working directory and index state WIP on AddThreadInfo: 98b6cf9 
Potential bug fix for TFrameAccountExplorer

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git status
On branch AddThreadInfo
Untracked files:
  (use "git add ..." to include in what will be committed)
src/gui-classic/Frames/UFrameThreadInfo.dfm
src/gui-classic/Frames/UFrameThreadInfo.pas

nothing added to commit but untracked files present (use "git add" to track)

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git add .

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git stash
Saved working directory and index state WIP on AddThreadInfo: 98b6cf9 
Potential bug fix for TFrameAccountExplorer

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git status
On branch AddThreadInfo
nothing to commit, working tree clean

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git switch RefactorCode
Switched to branch 'RefactorCode'
Your branch is up to date with 'origin/RefactorCode'.

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(RefactorCode)
$ git switch Release56
Switched to a new branch 'Release56'
Branch 'Release56' set up to track remote branch 'Release56' from 'origin'.

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(Release56)
$ git switch RefactorCode
Switched to branch 'RefactorCode'
Your branch is up to date with 'origin/RefactorCode'.

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(RefactorCode)
$ git status
On branch RefactorCode
Your branch is up to date with 'origin/RefactorCode'.

Changes not staged for commit:
  (use "git add ..." to update what will be committed)
  (use "git restore ..." to discard changes in working directory)
modified:   src/gui-classic/Frames/UFrameAccountExplorer.dfm
modified:   src/gui-classic/Frames/UFrameAccountExplorer.pas

no changes added to commit (use "git add" and/or "git commit -a")

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(RefactorCode)
$ git add .

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(RefactorCode)
$ git stash
Saved working directory and index state WIP on RefactorCode: 98b6cf9 
Potential bug fix for TFrameAccountExplorer

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(RefactorCode)
$ git switch AddThreadInfo
Switched to branch 'AddThreadInfo'

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git status
On branch AddThreadInfo
nothing to commit, working tree clean

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git stash
No local changes to save

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git stash pop
On branch AddThreadInfo
Changes not staged for commit:
  (use "git add ..." to update what will be committed)
  (use "git restore ..." to discard changes in working directory)
modified:   src/gui-classic/Frames/UFrameAccountExplorer.dfm
modified:   src/gui-classic/Frames/UFrameAccountExplorer.pas

no changes added to commit (use "git add" and/or "git commit -a")
Dropped refs/stash@{0} (a42b3cd36bab63af0ad033904f9666261028a12c)

Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git stash
Saved working directory and index state WIP on AddThreadInfo: 

Re: [git-users] Re: Make git aware of which machine did the git commits ?

[skybuck2000]

I tried to re-process it with vim:

 vim C:/Tools/Git/CustomUserSettings/.gitmessage

Also command to set it was:

 git config --global commit.template 
C:/Tools/Git/CustomUserSettings/.gitmessage

Problem with ^M remains, strangely enough, how hard is it to put some new 
lines in a text file and process it lol ? WOW:

^M
^M
Operating System: Windows 7 Home Edition^M
Virtualization Layer: VMWare Workstation 15^M
Virtual Operating System: Windows 11 Workstation Pro^M
Computer: Toshiba Laptop L670^M

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch AddThreadInfo
# Changes to be committed:
#   new file:   src/gui-classic/Frames/UFrameThreadInfo.dfm
#   new file:   src/gui-classic/Frames/UFrameThreadInfo.pas

Apperently I am missing something and there is some secret key ingredient 
needed to get rid of ^M

pff take about a waste of time... but I like this kind of detail 
hehehehehehe.

Though in this case it's getting a bit weird.

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/94e7d49b-b5dd-474b-9535-24b56c7b6d14n%40googlegroups.com.

[git-users] Re: Somehow git stash lost my changes.

[skybuck2000]

Oh this is odd:

Apperently git did not loose it confusing it is in there somewhere:


Skybuck@DESKTOP-0T9FP82 MSYS /e/SourceCode/PascalCoinGit/PascalCoin 
(AddThreadInfo)
$ git stash show
 src/core/ULog.pas|  2 +-
 src/core/UNetProtocol.pas| 12 +++
 src/core/UNode.pas   |  6 ++--
 src/core/UPCAbstractMem.pas  |  2 +-
 src/core/UPCOperationsBlockValidator.pas |  2 +-
 src/core/UPCOperationsSignatureValidator.pas |  2 +-
 src/core/UPoolMinerThreads.pas   |  6 ++--
 src/core/UPoolMining.pas |  2 +-
 src/core/URPC.pas|  4 +--
 src/core/UTCPIP.pas  |  6 ++--
 src/core/UThread.pas |  9 --
 src/gui-classic/UFRMAccountSelect.pas|  2 +-
 src/gui-classic/UFRMDiagnosticTool.pas   |  2 +-
 src/gui-classic/UFRMRandomOperations.pas |  2 +-
 src/gui-classic/UFRMWallet.dfm   | 48 

 src/gui-classic/UFRMWallet.pas   |  6 +++-
 src/gui-classic/UFRMWalletConfig.dfm | 18 +--
 src/gui-classic/UGridUtils.pas   |  6 ++--
 src/pascalcoin_wallet_classic.dpr|  3 +-
 src/pascalcoin_wallet_classic.dproj  |  5 +++
 20 files changed, 88 insertions(+), 57 deletions(-)

Perhaps when I did git stash pop it somehow did not apply it...

Well I don't need those changes anymore...

So git stash drop or something will probably get rid of it ;)

Bye,
  Skybuck =D

-- 
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/0bfd554d-acab-4905-9523-dbab78beb9ffn%40googlegroups.com.

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

[skybuck2000]

kfile and splitting it using a 
generic multi-volume archive tool (e.g., Unix split).

The minimum size allowed is limited to 1 MiB. The default is unlimited. 
Common unit suffixes of *k*, *m*, or *g* are supported.


receive.unpackLimit 

If the number of objects received in a push is below this limit then the 
objects will be unpacked into loose object files. However if the number of 
received objects equals or exceeds this limit then the received pack will 
be stored as a pack, after adding any missing delta bases. Storing the pack 
from a push can make the push operation complete faster, especially on slow 
filesystems. If not set, the value of transfer.unpackLimit is used instead.


receive.maxInputSize 

If the size of the incoming pack stream is larger than this limit, then 
git-receive-pack will error out, instead of accepting the pack file. If not 
set or set to 0, then the size is unlimited.


status.renameLimit 

The number of files to consider when performing rename detection in 
git-status[1] <https://git-scm.com/docs/git-status> and git-commit[1] 
<https://git-scm.com/docs/git-commit>. Defaults to the value of 
diff.renameLimit.

transfer.unpackLimit 

When fetch.unpackLimit or receive.unpackLimit are not set, the value of 
this variable is used instead. The default value is 100.

uploadpackfilter..allow 

Explicitly allow or ban the object filter corresponding to , where 
 may be one of: blob:none, blob:limit, object:type, tree, sparse:oid, 
or combine. If using combined filters, both combine and all of the nested 
filter kinds must be allowed. Defaults to uploadpackfilter.allow.


There are apperently many limits that GIT could run into. It would be very 
usefull if GIT could display which limit was hit and caused the 
failure/error. Ofcourse it would be better if GIT tries to function within 
these limitations so it does not error.

Bye for now,
  Skybuck.
On Thursday, December 2, 2021 at 6:01:36 AM UTC+1 skybuck2000 wrote:

> Hello,
>
> 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.
>
> Apperently GIT relies on PAGEFILE.SYS to cover any out of memory 
> situations.
>
> This kinda sucks.
>
> My recommendation is to disable PAGEFILE.SYS on your system, or try 
> removing some RAM chips.
>
> And then try and checkout the linux kernel yourself to see how GIT fails 
> to checkout.
>
> Also displaying a LOG seemed to consume also a lot of RAM.
>
> I am not exactly sure why GIT needs so much memory. Perhaps it's a 
> unzipping issue or a delta-ing issue, not sure.
>
> But it would be nice if GIT can do it's operations in 
> batches/chunks/pieces of memory.
>
> Gradually so it can handle any database size. Right now it seems to be 
> limited to the ammount of system RAM/virtual memory available.
>
> 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/44672e27-cca5-4c80-bfca-f38d967432fdn%40googlegroups.com.

[git-users] Re: GITK: Useability issue, can't scroll through file list with arrow key ?

[skybuck2000]

Hmm:

https://support.google.com/a/users/answer/9664435?hl=en

Seems this can only be done by group admin or something... I see the label 
icon at top right corner but it's says I don't have permission when I 
however over it... hmmm...

"
Apply or remove labels 

*Requires the Who can view conversations permission.*

Unlike labels you create in Gmail, a label you apply to a conversation in 
Google Groups is seen by anyone who can view that conversation.

   1. Sign in to Google Groups <https://groups.google.com/>.
   2. Click the name of a group.
   3. Choose an option to apply a label to or remove it from: 
  - A single conversation—Click the conversation.
  - Multiple conversations—Point to each conversationcheck the box next 
  to the poster's name.
   4. In the upper right, click Label .
   5. Begin typing the label namecheck or uncheck the box next to the name 
   when the label appears.
   Alternatively, you can create a new label to apply to the selected 
   messages.
   *Tip:* You can also remove a label by clicking a conversationat the top, 
   clicking *X* on the label name.

"

Requires the "Who can view conversations permission" ? Hmmm not entirely 
clear what this means haha.

Some special permission given to users of the group or something ?

Bye for now,
  Skybuck.

On Thursday, December 2, 2021 at 6:56:53 AM UTC+1 skybuck2000 wrote:

> How can I add a label to my postings ? I see labels on google groups.
>
> Is this done by somebody else or can I do it myself ?
>
> Bye,
>   Skybuck.
>
> On Thursday, December 2, 2021 at 6:55:38 AM UTC+1 skybuck2000 wrote:
>
>> I see two issues right now:
>>
>> 1. git gui does not have a link to gitk ?
>>
>> 2. I don't like clicking a lot with my mouse, hurts my finger, costs 
>> energy, and this mouse clicks badly, have to push it pretty hard, problem 
>> right now/useability issue with gitk:
>>
>> 2.1 clicking on right bottom view where it says "path" "tree" does not 
>> make gitk context aware.
>>
>> Desired behaviour:
>> when I press arrow key down on keyboard it should move to next file in 
>> that list.
>>
>> When I click back on a commit, next time I press arrow key down it should 
>> move through the commit list, this way the arrow key can be used to scoll 
>> through different lists depending on which list is "active" in other words 
>> "last clicked with mouse" or "navigated to with tab".
>>
>> Wrong behaviour:
>> instead git moves to the next commit.
>>
>>
>>
>> 2.2 The tab key also doesn't seem to lead immediately there and proceeds 
>> towards many other items first. Perhaps changing order to lead to right 
>> bottom screen might be more nice.
>>
>> 2.3 Perhaps there is a special key to switch to right bottom view ?
>>
>> Bye for now,
>>   Skybuck.
>>
>> P.S.: I am not sure exactly what gitk is used for or what the advantages 
>> or vs git diff ? For now it seems similiar ? Is git diff perhaps more 
>> powerfull ?
>>
>> How would I use gitk to compare to different commits or branches ? I saw 
>> a linus torvalds video/presentation about git for google, he mentioned gitk 
>> and how he could compare things ? Hmmm...
>>
>> I believe google may have used git to make android a success ! :) =D
>>
>

-- 
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/f9c1d980-b715-4332-8dd5-3118ea49bdc2n%40googlegroups.com.

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

[skybuck2000]

Hello,

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.

Apperently GIT relies on PAGEFILE.SYS to cover any out of memory situations.

This kinda sucks.

My recommendation is to disable PAGEFILE.SYS on your system, or try 
removing some RAM chips.

And then try and checkout the linux kernel yourself to see how GIT fails to 
checkout.

Also displaying a LOG seemed to consume also a lot of RAM.

I am not exactly sure why GIT needs so much memory. Perhaps it's a 
unzipping issue or a delta-ing issue, not sure.

But it would be nice if GIT can do it's operations in batches/chunks/pieces 
of memory.

Gradually so it can handle any database size. Right now it seems to be 
limited to the ammount of system RAM/virtual memory available.

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/ce998953-e9a2-4ca1-893a-0b151f6f72b2n%40googlegroups.com.

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

[skybuck2000]

Thanks !

Your command:

git rev-parse --abbrev-ref --symbolic-full-name @{u} 

Works by replacing  with the current branch name or any local 
branch name. (Does not seem to work with any remote branch name)

So far this limitation seems ok for now though if it could find any remote 
branch name that would be cool too.

Example that should work on most people's repository:

git rev-parse --abbrev-ref --symbolic-full-name master@{u} 

Question though:

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

The git documentation does not specify how to do that:

https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases

All examples seem to assume the parameter is at the end of the command ?

I know in dos I could use %1, %2, %3 but I am not familiar with bash.

One final question:

I did not get the part about the need to use the remote command ?

Do you mean to find the URL ?

Or do you mean that you have multiple remotes setup with the same alias ?

like 

origin url1
origin url2 

?

I am not sure if it's possible to setup multiple remotes with the same 
alias ? ;)

Or perhaps you mean that your command might return:

Git1 url
Git2 url
Git3 url

If there are multiple remotes with partially the same name ?

Bye,
  Skybuck.

On Wednesday, December 1, 2021 at 10:46:17 PM UTC+1 philip...@iee.email 
wrote:

>  git rev-parse --abbrev-ref --symbolic-full-name @{u}
>
> Had to look it up yesterday. Then you need
>
> git remote -v   # or -vv
>
> to find out where that remote really is!
> - I have 10 remotes for variations of 'git' itself, including "my" which 
> is my publish remote.
>
> On Wednesday, December 1, 2021 at 2:51:06 PM UTC skybu...@hotmail.com 
> wrote:
>
>> It would be usefull if there was a command to see the tracking 
>> information for the current branch, if any.
>>
>> Right now I am trying to figure out if any tracking is set for the local 
>> branch to some kind of remote branch.
>>
>> There does not seem to be a command for it ?
>>
>> I know there are other commands to display all: git branch -vv
>>
>> However if the number of branches become very large, I may end up having 
>> to search through such a list.
>>
>> Displaying such a huge list also distracts from the rest of the git 
>> command flow.
>>
>> So something more tiny would be appreciated.
>>
>> 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/1767abbd-ee09-427b-8c57-c74882eebb1bn%40googlegroups.com.

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

[skybuck2000]

I see two issues right now:

1. git gui does not have a link to gitk ?

2. I don't like clicking a lot with my mouse, hurts my finger, costs 
energy, and this mouse clicks badly, have to push it pretty hard, problem 
right now/useability issue with gitk:

2.1 clicking on right bottom view where it says "path" "tree" does not make 
gitk context aware.

Desired behaviour:
when I press arrow key down on keyboard it should move to next file in that 
list.

When I click back on a commit, next time I press arrow key down it should 
move through the commit list, this way the arrow key can be used to scoll 
through different lists depending on which list is "active" in other words 
"last clicked with mouse" or "navigated to with tab".

Wrong behaviour:
instead git moves to the next commit.



2.2 The tab key also doesn't seem to lead immediately there and proceeds 
towards many other items first. Perhaps changing order to lead to right 
bottom screen might be more nice.

2.3 Perhaps there is a special key to switch to right bottom view ?

Bye for now,
  Skybuck.

P.S.: I am not sure exactly what gitk is used for or what the advantages or 
vs git diff ? For now it seems similiar ? Is git diff perhaps more 
powerfull ?

How would I use gitk to compare to different commits or branches ? I saw a 
linus torvalds video/presentation about git for google, he mentioned gitk 
and how he could compare things ? Hmmm...

I believe google may have used git to make android a success ! :) =D

-- 
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/67d15a08-85af-46da-96d8-4ec6262ae1cen%40googlegroups.com.

[git-users] Re: GITK: Useability issue, can't scroll through file list with arrow key ?

[skybuck2000]

How can I add a label to my postings ? I see labels on google groups.

Is this done by somebody else or can I do it myself ?

Bye,
  Skybuck.

On Thursday, December 2, 2021 at 6:55:38 AM UTC+1 skybuck2000 wrote:

> I see two issues right now:
>
> 1. git gui does not have a link to gitk ?
>
> 2. I don't like clicking a lot with my mouse, hurts my finger, costs 
> energy, and this mouse clicks badly, have to push it pretty hard, problem 
> right now/useability issue with gitk:
>
> 2.1 clicking on right bottom view where it says "path" "tree" does not 
> make gitk context aware.
>
> Desired behaviour:
> when I press arrow key down on keyboard it should move to next file in 
> that list.
>
> When I click back on a commit, next time I press arrow key down it should 
> move through the commit list, this way the arrow key can be used to scoll 
> through different lists depending on which list is "active" in other words 
> "last clicked with mouse" or "navigated to with tab".
>
> Wrong behaviour:
> instead git moves to the next commit.
>
>
>
> 2.2 The tab key also doesn't seem to lead immediately there and proceeds 
> towards many other items first. Perhaps changing order to lead to right 
> bottom screen might be more nice.
>
> 2.3 Perhaps there is a special key to switch to right bottom view ?
>
> Bye for now,
>   Skybuck.
>
> P.S.: I am not sure exactly what gitk is used for or what the advantages 
> or vs git diff ? For now it seems similiar ? Is git diff perhaps more 
> powerfull ?
>
> How would I use gitk to compare to different commits or branches ? I saw a 
> linus torvalds video/presentation about git for google, he mentioned gitk 
> and how he could compare things ? Hmmm...
>
> I believe google may have used git to make android a success ! :) =D
>

-- 
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/8ce1d83e-e6b4-4c8a-bf6f-69c621b835fan%40googlegroups.com.

[git-users] Rebase documentation is not clear enough.

[skybuck2000]

https://git-scm.com/book/en/v2/Git-Branching-Rebasing

I believe git rebase must be done from the branch which is to be re-based.

So it's always necessary to git switch 

It is not possible to go to git switch 

and then do git rebase  etc

This will not work and go wrong correct ?!?

If so, then the documentation at this link is not clear:

https://git-scm.com/book/en/v2/Git-Branching-Rebasing

There are some re-base commands without a clear git switch 


This makes it seems like it's possible to issue this command from any 
branch.

Documentation should be updated and make clear that user has to been on the 
branch that is to be rebased.

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/925660e3-4a00-497d-a10a-f198e30090ffn%40googlegroups.com.

[git-users] Re: GIT: Split file into multiple files, then detect changes in updated original file and apply to multiple files.

[skybuck2000]

Split all at once so far not succeeded, individual branches offer some 
help, by allowing git -mv to indicate to git that a big file was 
renamed/reduced to a small file.

Then later all individual branches can be merged to produce a build.

The problem with this is if changed are done to  the new build, and later 
to old build, changes from new build get lost or have to be re-applied to 
individual branches again.

What I would need here is a way to tell git that a big file should be 
copied/applied multiple times to individual parts/files ?

So for example:

Apply BigFile to LittleFile1 LittleFile2 LittleFile3

There seem to be some git plumbing commands.

Maybe there is some plumbing command that can help with this.

Bye for now,
  Skybuck.

On Tuesday, November 23, 2021 at 1:30:48 AM UTC+1 skybuck2000 wrote:

> GIT: Split file into multiple files, then detect changes in updated 
> original file and apply to multiple files.
>
> File Original contains:
>
> ObjectA
>
> Some funtions for Object A
>
> some more functions for Object A
>
> ObjectB
>
> Some functions for Object B
>
> some more functions for Object B
>
> ObjectC
>
> Some functions for Object C
>
> some more functions for Object C
>
>
> This should be split up into three files:
>
> ObjectA
>
> ObjectB
>
> ObjectC
>
>
> Such that File ObjectA contains:
>
> ObjectA
>
> Some funtions for Object A
>
> some more functions for Object A
>
>
> Such that File ObjectB contains:
>
> ObjectB
>
> Some funtions for Object B
>
> some more functions for Object B
>
>
> Such that File ObjectC contains:
>
> ObjectC
>
> Some funtions for Object C
>
> some more functions for Object C
>
>
> Later file Original is updated:
>
> ObjectA
>
> Some funtions for Object A
>
> some more functions for Object A
>
> even more functions for Object A
>
> ObjectB
>
> Some functions for Object B
>
> some more functions for Object B
>
> even more functions for Object B
>
> ObjectC
>
> Some functions for Object C
>
> some more functions for Object C
>
> even more functions for Object C
>
>
> Is it somehow possible to use git to automate the updating of File 
> ObjectA, File ObjectB File ObjectC so that all three files contain the new 
> line such that:
>
>
> Such that File ObjectA contains:
>
> ObjectA
>
> Some funtions for Object A
>
> some more functions for Object A
>
> even more functions for Object A
>
>
> Such that File ObjectB contains:
>
> ObjectB
>
> Some funtions for Object B
>
> some more functions for Object B
>
> even more functions for Object B
>
>
> Such that File ObjectC contains:
>
> ObjectC
>
> Some funtions for Object C
>
> some more functions for Object C
>
> even more functions for Object C
>
>
> This is a scenerio where the original file is updated by a different user.
>
> It would be very nice if a feature git had this detection capability for 
> two reasons:
>
>1. 
>
>Big teams/projects that might not want to freeze such a big fle.
>2. 
>
>No-cooperating teams/repository that don't want to split the file.
>
>
> Now that I understand git a little bit better, very maybe this will work:
>
> What could be tried for the split dilemma, is the following idea:
>
>
> 1. The original document.txt is splitted in a "split commit" such that 
> objecta.txt objectb.txt and objectc.txt exist.
>
> 2. This "split commit" can be isolated on top of original document.txt or 
> anywhere basically.
>
> 3. Then when original document.txt is updated, try and reapply the "split 
> commit", by basically re-basing it on top of the updated document.txt
>
> So in git terms the idea is as follows:
>
> BranchOriginalDocument   commit 1
> document.txt
> BranchSplittedDocument commit 2
> objecta.txt
> objectb.txt
> objectc.txt
> (could even be placed on their own sub branch if necessary because one 
> branch might not be enough)
> BranchUpdatedDocumentcommit 3
> document.txt
> 
> now after after commit 3 is done, commit 2 could be rebased onto commit 3 
> in the hopes that git will recgonize the split operation and maybe
> repeat it on top of document.txt with updated contents.
>
> the git command for this would like something like:
>
> git rebase --onto BranchUpdatedDocument BranchOriginalDocument 
> BranchSplittedDocument
>
> tomorrow I will give this a try to see how far I get with this.
>
> If it fails one more try would be to create additional branches or so, I 
> s

[git-users] Driving a little train (dot/point/circle) across the branches.

[skybuck2000]

 It would be nice if there was some kind of train/vehicle/dot/point/circle 
that could be moved across the branches.

For example on the output of git log --graph --all.

By using the cursor keys the train/dot can then be moved up,down,left,right.

Left,Right to change/choose branch, Up/Down to move forward or backward 
through commits.

Left/Right should highlight which branch is selected.

Press enter should then automatically git checkout the commit that the 
train/dot is on.

This prevent me from having to type and copy & paste hash codes and it also 
integrates the scrolling up and down with travelling across branches a bit 
more easy.

So I would like this functionality implemented in git.exe so it can be used 
from command lines/git bash/cmd.exe/powershell/git posh etc.

(If you like idea and you on git mailing list, mail this forward to them ! 
Cause for some reason I can't and not yet gonna subscribe, see ya ! =D)

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/35fc64ac-0b59-4662-859e-5a780a8bf5een%40googlegroups.com.

Re: [git-users] Driving a little train (dot/point/circle) across the branches.

[skybuck2000]

On Saturday, January 15, 2022 at 5:29:59 PM UTC+1 Magnus Therning wrote:

>
> Maybe https://jonas.github.io/tig/ fits the bill. 
>
>
>From the description and visuals it seems like this may allow to drive 
around like a choo choo train, but with extras... not yet sure I like the 
extras...

I asked for just driving around, but ok, maybe the extra can be 
ignored/disabled, or maybe it just gets in the way but it's interesting.

I am too tired to install yet another git prompt thingy... but tomorrow I 
will probably give this TIG a try... What does TIG stand for ? Hmmm

Anyway I watch this video today, it seems somewhat familiar/similiar, Is 
this guy also using TIG ? Or is just the greenness is similiar ? Hmmm...

https://www.youtube.com/watch?v=g-WPhYREFjk

^^ CPP branchless optimization guide... which kinda interesting.

However the most important question/mystery is not answered, now I still 
don't know...

Why the function pointer table trick don't work well ? H... addressess 
to far seperated from each other or something ?

Bad instruction loading ? Hmmm..
  

>
> -- 
> Magnus Therning OpenPGP: 0x927912051716CE39 
> email: mag...@therning.org 
> @mag...@mastodon.technology http://magnus.therning.org/ 
>
> Computers are useless. They can only give you answers. 
> — Pablo Picasso


LOL Funny. 

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/ea530f4e-e67d-4577-8edc-cec030216cd7n%40googlegroups.com.

Re: [git-users] Is it possible to apply git versioning/diffing algorithm to multiple files which are the same file ?

[skybuck2000]

>
> > What I would like also is for these differences to be visible on 
> > github/commits. 
>
> This is not possible due to the reasons I have presented above. 
>
>
I am going to assume you did not read the rest of my post or it wasn't 
clear. So I will repeat the "minimum" idea I had to make this possible:

1. git diff version1.txt version2.txt

2. store the difference in version1vs2_differences.txt

3. "upload" version1vs2_differences.txt to github.

Are you now "saying" that this is somehow not possible because the git diff 
output inside version1vs2_differences.txt will confuse git ?

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/4ef0f4df-fd4b-409d-839e-a1bb6441731en%40googlegroups.com.

Re: [git-users] Is it possible to apply git versioning/diffing algorithm to multiple files which are the same file ?

[skybuck2000]

On Friday, March 4, 2022 at 9:49:49 AM UTC+1 Konstantin Khomoutov wrote:

> On Thu, Mar 03, 2022 at 11:12:08PM -0800, skybuck2000 wrote: 
>
> >> There's no such support built into Git (because this simply goes 
> >> perpendicular to its data model, where multiple versions are recorded 
> for 
> >> the same file (well, actually, they are recorded across the content of 
> all 
> >> the files in the project 
> [...] 
> > What I would like also is for these differences to be visible on 
> > github/commits. 
>
> This is not possible due to the reasons I have presented above. 
>
> You can commit the addition of file1.txt, then commit the addition of 
> file2.txt which contents is based on that of file1.txt, but this does not 
> mean 
> anything to Git: there are two different files. 


I was under the impression that GIT calculates a hash based on the contents 
and can somehow detect same content.

Now it appears this is not the case, so this is a bit weird.

I guess this only applies if the content is exactly the same, and only the 
filename changed, perhaps only then git can detect a "rename".

(I tried adding version1.txt and version2.txt and version3.txt each on 
their own commit, git was unable to detect that these are the same file and 
that these files evolved, this sucks and is a weakness in git, it stops 
people from transitioning from a "natural" / "manual" / "intuitive" 
versioning system towards git :( )
 

> Think of it this way: suppose 
> your project has 100k files (think of Linux, for instance), and in a 
> particular commit you change two of them - do you expect Git to show you a 
> set 
> of differences between each of these files and 9 other files, totaling 
> 2×9 differences? I hope not. 
>

I don't see how this has anything to do with my problem :)
 
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/36c9af5f-389c-420a-b0e2-ed429b5a893an%40googlegroups.com.

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

[skybuck2000]

Oh, Oh...

So while I was waiting for the linux kernel to checkout I was reading some 
random stuff about operating systems, or mostly linux boot loaders other os 
loaders and some people on github involved with linux and then I switch 
back to the linux checkout and I notice this:

new@new-PC MINGW64 /e/SourceCode/LinuxKernelWorkAround
$ git clone https://github.com/SkybuckFlying/linux.git
Cloning into 'linux'...
remote: Enumerating objects: 8590563, done.
remote: Counting objects: 100% (23/23), done.
remote: Compressing objects: 100% (23/23), done.
remote: Total 8590563 (delta 9), reused 0 (delta 0), pack-reused 8590540
Receiving objects: 100% (8590563/8590563), 3.49 GiB | 9.28 MiB/s, done.
fatal: Out of memory, malloc failed (tried to allocate 214601 bytes)
fatal: index-pack failed

BM... failed.

SUCKS.

My recommendation is to PAUSE git if it runs out of memory cause enabling 
pagefile.sys is a big fat no-no as far as I am concerned and I am never 
ever going back to pagefile.sys or any other disk caching technology cause 
it SLOWS down my SYSTEM(S) incredibly and therefore IT SUCKS.

This crash of git was probably caused by the memory consumption of firefox 
and webpages and blabla.

But fear not I will try again over"night" when I go to "sleep" (don't hack 
me bro hahaha !) and then my poor little laptop with 6 GBs of RAM can try 
one more time without me fucking up the process by taking up RAM bleh.

And if that fails... well holy fok ! At least the shallow clone trick 
worked but common THIS IS GIT.

So FAR GIT was pretty good, but this is the first time GIT massively FAILS 
and is not capable of copeing with THE SKYBUCK LOL.

You know I have better things to do then wait 6 hours for a linux git 
checkout ?! Do you see my point ?!

This is definetly something where GIT should be made more reliable !

Don't give me wrong, GIT impresses me many times, but this one 
NPPPE p: p: p: THUMBS DOWN.

Invest some of your time writing out of memory resistant computer 
programs/GIT versions it may be worth it someday when we hit BIG FAT 
TRANSISTOR scaling down/up issues whatever. HAHA.

Memory does not grow on trees lol. SOME DAY moore's lllaw will come to an 
END... start preparing for it ! 

Here is some helpfull hints:

TryAlloc

instead

of Alloc

write it like

if TryAlloc(...)
{

}

OK ?

Believe me it's not that hard, it just requires some time.

And in case you didn't get it here is how you may implement TryAlloc

int TryAlloc( ...)
{
  try
 Alloc
 return true
  catch exptions
return false
}

Something like that.

Good luck !

One last tip, also check for storage space if git runs out of storage space.

Pause the program, possibly with a dialog screen or even better, terminate 
the command and make it possible to continue the command later... if that 
is too difficult... at least pause
the command and make the user hit a button to continue and try again.

Again not that hard and well worth it.

This allows the users to free up space, to continue these kinds of long 
processes.

And let's be honest there is no indicator how much space a checkout 
requires so sooner or later people will run out of space.

For now with big terrabyte disks, not yet a problem... then again... my 
disks after a few years pretty full, cause there is so much fun toy stuff 
out there... and again moore's law will strike the harddisk world as well 
someday ! Prepare for it ! Yeah

And in cause you don't believe me my own UDP File Transfer already does all 
of it that I wrote above :P*

Yes and I have also have an unreleased version which can do 64 bit file 
transfer instead of just 32 bits.

Perhaps a simpler program then again it's also complex enough that it 
proves it can be done (in Delphi and I am sure C/C++ can do it as well, 
cause Delphi is mostly a subset of C/C++)

Bye,
  Skybuck.  (I mean it, get this done !)

-- 
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/e600184e-911a-4647-9fd9-d596976f9093n%40googlegroups.com.

[git-users] Is it possible to apply git versioning/diffing algorithm to multiple files which are the same file ?

[skybuck2000]

So suppose I have a repo which is like this:

version1.txt
version2.txt
version3.txt

All three files are actually the same file.

Is it possible to tell git that version3.txt was based on version2.txt and 
version2.txt was based on version1.txt and that it should apply it's 
difference engine onto it ?

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/def47d4d-e655-4f8c-a33c-e4b4702b8405n%40googlegroups.com.

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

[skybuck2000]

Hi,

My latest hypothesis what might have happened during that normal git 
checkout on linux kernel is that there was some kind of memory 
fragmentation and windows could not return enough memory.

Test programs could be written to test this hypothesis but I have no time 
for this.

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/5d96ea15-0a25-4b45-a434-030703157853n%40googlegroups.com.

[git-users] Improved Solution for Ukraine vs Russia

[skybuck2000]

Watch these two videos, very important:

Professor:
https://www.youtube.com/watch?v=JrMiSQAGOS4=3107s

Skybuck:
https://www.youtube.com/watch?v=ply4Se_bVws

Greetings,
   Skybuck Flying! 

P.S.: I am very sorry for posting this off-topic posting, but if this has 
even a very slight chance of reaching people in power to stop this then 
it's worth it.

-- 
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/e7b13c53-ca93-48ec-96a2-9c6c6759c68cn%40googlegroups.com.

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

[skybuck2000]

On Thursday, March 3, 2022 at 3:54:25 PM UTC+1 philip...@iee.email wrote:

> > Am I correct in that the work to make mainline Git use size_t where 
> applicable 
> is ongoing? 
>
> It's currently a little stalled, because it's been hard to partition the 
> problem into small chunks that fit everyone's expectations about what 
> should be in or out for tidying up consequences (e.g. large call chains). 
>
> It's not really clear if "size_t" is considered a nice data type, along 
> with `ssize_t` to be replacing `ulong` and `long`, as they tend to make the 
> code feel "ugly". 
>

Consider porting git to Delphi =D

Anyway here is a tip from the Delphi world, in Delphi there is this type 
called:

NativeInt

and

NativeUInt

These two types auto-adjust to the maximum/natural integer size of the 
system.

So if it's 32 bit NativeInt would be 4 bytes.
So if it's 64 bit NativeInt would be 8 bytes

I think this is a much nicer description than size_t or ssize_t LOL.

Bye,
  Skybuck =D

-- 
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/d837f25f-61b9-454a-a6ee-f0694da73575n%40googlegroups.com.

Re: [git-users] Is it possible to apply git versioning/diffing algorithm to multiple files which are the same file ?

[skybuck2000]

>
>
> There's no such support built into Git (because this simply goes 
> perpendicular 
> to its data model, where multiple versions are recorded for the same file 
> (well, actually, they are recorded across the content of all the files in 
> the 
> project, but let's not digress)) but you can use Git's command to do what 
> you're after: 
>

What I would like also is for these differences to be visible on 
github/commits.

- `git diff` can work on files.


Yes I have seen this before, but it was not quite intuitive... I would 
expect it to work with

git diff filea fileb 

but from what I can remember it may have to work differently based on what 
files are in the repo, though I could be wrong, tomorrow I will experiment 
some more with this git diff and creating patches.
 

>
> - `git apply` and `git am` can be used to apply what `git diff` generates 
> - 
> this is called "unified diff format" - to the specified file(s).


I have heard about "patches", "git patches", "applieing git patches", 
"e-mailing git patches" and such but never really done it so this is a bit 
interesting to try this out.

At least this is a start and offers something to try and get these 
differences and store them.

So for now my idea is to create some kind of patch/patch files and then 
store them on the repo in case I want to store these differences and then 
in principle people can click those difference files on github and can see 
the differences in this git diff format.

But I have a feeling this will be less ideal because it will probably be 
somewhat confusing and will probably not "play ball" with github though I 
may be surprised. On the other hand the difference visualization on github 
is not too great anyway... meld or other tools might be better but for 
quick web access github is kinda nice.

However noobies or maybe even nobody might understand what these patch 
files are but then that is up for me to describe.

It would be nice to record at least these changes somewhat, it would be 
even nice if this could be automated... I am sure somebody could come up 
with a script, but then it might become somewhat painfull if I have to 
start using scripts everywhere for such versioning files.

So then one could say, just leave the version information out but I have 
some objections against that because then it becomes hard to actually know 
which file in the repo/which commit is actually an intact version or a next 
version.

Another solution could be to use git tags, but then versioning is lost if 
these tags disappear or git stops being used, and there is another 
disadventages to not using multiple versions, it's a pain in the ass to 
switch to older versions/commits, creating a worktree just to fetch one 
older file is a pain in the ass. Plus here is thus also where git gets 
messy when it comes to versioning and keeping version implementations 
seperated, this is where git truely starts to "flow" to much into each 
other and this is a complained against how git handles this and here I feel 
git somewhat falls short and should get some kind of true version number 
feature to version files properly, and maybe even start a versioning 
"revolution" where programmers actually start liking to version their files 
properly ! ;)

Now there are some disadventages as to have to replace version numbers 
everywhere it's used when it increments that is true, but this can also be 
considered a major adventage because now the compiler will complain about 
missing old version if it was removed from project and hence you as a 
programmer get automatic support from the compiler to check exactly which 
files are updated because of a new version being used, so this gives more 
control over "transitioning" to a new version. Sometimes this may be 
overkill, or annoying or time wasting, or undesired, but on the other hand 
it can also give re-assurence that everything is fine cause you re-checked 
most of it.

Now spending so much time on re-versioning things is somewhat of a time 
waster so I don't try to use it too much but I have seen situations where 
not versioning quickly would be much more horrible... and this is where git 
falls short. Committing unfinished or broken versions also seems not a good 
idea, so quickly renaming files and incrementing their version number is a 
much quicker/easier and saver way to quickly interate over versions of 
files/implementations, keeping multiple files consistent by changing all of 
their version numbers so that programmer knows they belong together.

Without proper versioning of files it becomes much harder to tel if a 
certain file was properly changed to fit the new version... it becomes 
confusing to say the least and previous work/data/code could be lost much 
easier since it's overwritten by newer versions/implementations. Again this 
is where git falls short and needs some kind of future to quickly and 
safely version files.

The closest thing I have seen so far that comes 

Re: [git-users] Is it possible to apply git versioning/diffing algorithm to multiple files which are the same file ?

[skybuck2000]

This is a fun post/article which describes the "revision" problem:

https://www.makeuseof.com/tag/file-versioning-git/

However this problem is only present in "multi-programmer" projects.

As long as only one programmer is working on files for some kind of big 
changes, this is not a problem.

Thus this article is a bit quick on to dismiss this revision technique.

I can understand how something like this might get messy if everybody 
starts editing the same revision number etc... and put there names in front 
of it, and maybe messages etc.

But what is the alternative ? Strange branch names ? Etc ? Some kind of 
description has to be given anyway.

Anyway I go read that article a bit more to see if they have any solution 
and to see if it changes my mind.

But I can already tell you: for single-programmer development, most likely 
no way LOL =D

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/860a6c81-b939-4731-89d4-c2e92205d7b3n%40googlegroups.com.

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

[skybuck2000]

On Thursday, March 3, 2022 at 11:42:54 AM UTC+1 Konstantin Khomoutov wrote:

> On Wed, Mar 02, 2022 at 06:03:46PM +, Skybuck Flying wrote: 
>
> >> Search for "4GB" in this blog post [1] which discusses the GfW 2.35 
> release 
> >> notes. 
> >> 
> >> 1. https://github.blog/2022-01-24-highlights-from-git-2-35/ 
>
> > Thanks for the update, however I don't see how this could effect git 
> > checkout of linux kernel, since most linux source files are only a few 
> > kilobytes... 
>
> Because Git has several data storage/transfer optimization tricks. One of 
> them 
> is using of so-called "pack files" (basically that's the behind-the-scenes 
> mechanism that allows Git to remain fast and have modest storage 
> requirements 
> while its data model states that each commit is a snapshot of the whole 
> project). Pack files are used for both storing stuff on the filesystem, 
> and 
> for data transfer; they basically are gzipped archives with added index 
> files 
> for fast random access to the contained data. 
>

Depends on how these pack files are used, if only parts of them are 
read/written then it does not need to be a problem :)

Also I did not see any big spikes in memory consumption, at least when I 
was paying attention.
 

>
> My take is that processing of such a pack file hits some limit of the 
> current 
> GfW implementation, which has nothing to do with the OS limits (given that 
> up-to-date API calls are used). 
>

What is GfW ?

Firefox also fails regularly when many tabs open, it only does this when 
pagefile.sys is off.

So as far as I am concerned it clearly has something to do with the memory 
system in windows which is probably less well tested when pagefile.sys is 
off because most systems/default installation have a pagefile.sys, 
therefore I recommend any serious programmer working on serious project to 
turn off pagefile.sys or swap space and observe the memory system ! I am 
sure you will be surprised ! =D
 

>
> While I think such problems were actually solved some time ago, some may 
> still 
> remain. In any case, it's hard to say something w/o proper bug report - 
> either 
> in the project's tracker of at least on the git-for-windows mailing list. 
>

Why would that make any difference ? Are you hoping for developer feedback 
on this issue ?

I did mention the error message but in case you missed it here it is one 
more time:

fatal: Out of memory, malloc failed (tried to allocate 214601 bytes)
fatal: index-pack failed  

So from this I can see two things:

1. It was trying to allocate a 214 kilobyte block which is quite large and 
makes the fragmentation hypothesis somewhat believable since windows uses 4 
kilobyte pages as far as I know and these are stored in "lists". So to 
forfill this request it needs  214601 / 4096 = 53 pages. Now maybe a 
statiscian can somehow calculate the chance of 53 consequetive pages being 
present without any gaps/missing ones, especially when the system is under 
heavy use trying to create many little C files or whatever it was doing. 
>From what I remember it was resolving deltas... so it seems git was 
"replaying" changes and these could be made out of many many many little 
changes, hence this makes the memory fragmentation hypothesis believeable.

Also what kind of file would need 214 kilobytes ? Perhaps linux has a file 
of that size, maybe some documentation or so, though I have also seen big 
lookup tables in other software like bitcoin 256psek or something and 
pascalcoin and regex/unicode lookup table which is slowing down or freezing 
analysis tools so this is not good.

2. Indeed it's doing something with an index-pack file... so this is 
probably what you based your analysis on so you did read the bug/error 
report that I posted :)
So this could mean it was extracting something or maybe indeed packing 
something up, but it wasn't that big... and it was computing some index 
file.

For now the easy assumption is to assume the system simply run out of 
memory, but this is a suspicious/somewhat bad conclusion because the chart 
in the video does not really back that hypothesis up, and also as far as I 
can re-call the browser was not crashing and seemed to be doing fine, now 
maybe it simply had enough memory to do it's thing, but usually the browser 
can suddenly take up a lot of memory and crash quite easily... then 
again... since git is using many little files... maybe it just hit it 
sooner and is more sensitive to out of memory or something, though it could 
also be memory fragmentation or a combination. For now the memory 
fragmentation or in combination with system cache taking up precious memory 
is believeable because other people have noticed strange behaviour with 
windows 7.


> By the way, do you use a 64-bit install? If, for some reason, you're using 
> a 
> 32-bit version, the limit of circa 4 GB (actaually lower) will be 
> "native". 
>
>
new@new-PC MINGW64 /
$ file $( which git )
/mingw64/bin/git: PE32+ executable 

Re: [git-users] Is it possible to apply git versioning/diffing algorithm to multiple files which are the same file ?

[skybuck2000]

On Friday, March 4, 2022 at 8:23:58 AM UTC+1 skybuck2000 wrote:

> This is a fun post/article which describes the "revision" problem:
>
> https://www.makeuseof.com/tag/file-versioning-git/
>
>
>
Read a bit further into it.

What I could do is rename the versioned files back to the original.

So example:

module.txt
module_version1.txt
module_version2.txt
module_version3.txt 

When I am done with module_version4.txt I could rename it back to module.txt

But ofcourse do you seem the problem ?

This kinda feels akward and might make more confusion then it's worth it... 
then again maybe not if looking at the files in a timeline...

Deleting v1,2,v3 is very much undesireable.

So this is a very clear situation where GIT is now fighting and in conflict 
with existing versioning information.

Basically once files are versioned as described above GIT becomes useless 
or confusing at best, hence a solution should be made/found for this to 
make GIT interoperable with versioning systems as described above.

The completely lack/loss of versioning information in most projects on 
github/git repos is kind of concerning it gives a lack of sense of much 
change a file has experienced.

There is very little indication except for the lastest timestamp... but 
this could also be misleading.

Currently at best what I have seen is a "linux rc6" or a "pascal coin 
release tag 5.4" this is then some tag slammed onto all files at the 
project at large.

Fine-grained per file versioning information and change velocity is 
completely lost it seems, quite a shame in a way.

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/0a9bf0a8-9899-4bb9-98ef-0244aab86eben%40googlegroups.com.

Re: [git-users] Is it possible to apply git versioning/diffing algorithm to multiple files which are the same file ?

[skybuck2000]

One possibility which comes to mind is to go "back in time" and create some 
more commits/branches or whatever.

And spread these different versions over multiple commits.

So one commit per version.

Very maybe git will then recognize these different versions as being the 
same file and then it can properly/automatically diff them.

(It may recgonize them as "renames" or "moves")

This is worth a try.

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/11dfb8fb-8ac9-4eee-ae1a-ab96b8148ce6n%40googlegroups.com.

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

[skybuck2000]

Hello,

I am back in this thead on 28 february 2022. I read that linux will soon 
move to a new compiler/c language version, from C89 to C11 so I thought I 
would try again to checkout the linux kernel so that I can see what it 
looks like.

But surprise surprise, it fails again.

This time I record it on video, since nowadays I have streaming software on 
this 6 GB RAM toshiba laptop that can stream directly to youtube saving me 
a lot of time.

So it turns out that 3 files cannot be checked out because they start with 
the filename: "aux" and this is forbidden on windows 7 at least and also 
windows 10 according to other people.

Link to youtube video that shows the problem at timestamp 8 minutes and 20 
seconds: 

https://youtu.be/n15JnFgaxKs

I think this is what might have happened the first time I tried this, 
making me believe it may have been some out of memory situation or maybe I 
was running a virtual machine and the memory was divided in two pieces 3 
gigabyte each. But this time the laptop had 6 GB of RAM. Still 2 gigabyte 
free when this error occured.

So I no longer believe it's an out of memory situation, but something 
entirely else. Some kind of bug possibily deep within git, git may have to 
work around this and simply skip over files that have illegal file names on 
windows. or should try and rename it.

Anyway is there a solution that would allow me to checkout most of it ? 
Cause I just want to have a looksy that is all for now.

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/b2e43080-9b6a-4fa6-a322-f86261226447n%40googlegroups.com.

[git-users] Official Linux Repository cannot be checked out because of illegal "aux" filenames on Microsoft Windows !

[skybuck2000]

 Hello,

On windows 7 and windows 10 it is illegal to start a filename with "aux".

Example:

new@new-PC MINGW64 /e/SourceCode/LinuxKernel/linux (master)
$ git checkout master
error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.c'
error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.h'
error: invalid path 'include/soc/arc/aux.h'

Link to youtube video that shows the problem at timestamp 8 minutes and 20 
seconds: 

https://youtu.be/n15JnFgaxKs

How can I still checkout most of the files, is it possible to somehow just 
skip over these 3 files ?

Or are you telling me the Linux Kernel source is now stuck forever inside 
this Repository and it cannot be extracted anymore ?!

If so that is horrorific and exactly one or my worries with using systems 
like git.

Bye,
  Skybuck Flying.

-- 
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/ee5b5718-8412-487b-96b2-c4f65070a764n%40googlegroups.com.

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

[skybuck2000]

It doesn't hurt to have a little bit of redundancy, especially for 
something as "important" as the linux kernel lol:

(Copy & Pasting this posting/solution to this thread as well)

For now the solution I came up with is to:

1. Trust that this github repository is from "official sources":

https://github.com/torvalds/linux

2. Clone it.

3. Rename these 3 files remotely/on the repository via github and it's file 
editing feature, which fortunately also allows a rename of file.

error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.c'
error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.h'
error: invalid path 'include/soc/arc/aux.h' 

To 

WorkAroundAux.c and such.

By the way, this "aux" is a limitation inside NTFS file system, so linux 
can be affected as well. Also directories with aux in it will have the same 
problem.
Not sure if "auxbla" or 'blaaux" will cause it. For now I assume that if it 
starts with "aux" it's illegal.

I haven't tried yet, but I am pretty sure this is going to work. If not 
then I will report back here. If I run into any other problem, then maybe 
too or I go into that other thread if 6 GB of RAM is not enough to checkout 
the linux kernel ;) ;) ;) yes winks... that could be another reason, to 
never use one of these systems for any serious source code work, because 
again that would be horrible not to be able to access your source code :P*

Oh yeah before I forget, why is this:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

It does not mention the linux repository on github ?

Is the Linus Torvalds account on github REAL ? Or is it fake ? Is there 
anyway to be sure ? Maybe some kind of signature check from a mailing list 
or something where he announces he joined github ?

This is supposed to be his account: is it real ?

https://github.com/torvalds

If it is real then why does it not mention so on this page ?:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Bye for now,
  Skybuck =D

-- 
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/978dd2b3-372c-44fd-b214-8fcbcec9bfeen%40googlegroups.com.

[git-users] Re: Official Linux Repository cannot be checked out because of illegal "aux" filenames on Microsoft Windows !

[skybuck2000]

For now the solution I came up with is to:

1. Trust that this github repository is from "official sources":

https://github.com/torvalds/linux

2. Clone it.

3. Rename these 3 files remotely/on the repository via github and it's file 
editing feature, which fortunately also allows a rename of file.

error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.c'
error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.h'
error: invalid path 'include/soc/arc/aux.h' 

To 

WorkAroundAux.c and such.

By the way, this "aux" is a limitation inside NTFS file system, so linux 
can be affected as well. Also directories with aux in it will have the same 
problem.
Not sure if "auxbla" or 'blaaux" will cause it. For now I assume that if it 
starts with "aux" it's illegal.

I haven't tried yet, but I am pretty sure this is going to work. If not 
then I will report back here. If I run into any other problem, then maybe 
too or I go into that other thread if 6 GB of RAM is not enough to checkout 
the linux kernel ;) ;) ;) yes winks... that could be another reason, to 
never use one of these systems for any serious source code work, because 
again that would be horrible not to be able to access your source code :P*

Oh yeah before I forget, why is this:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

It does not mention the linux repository on github ?

Is the Linus Torvalds account on github REAL ? Or is it fake ? Is there 
anyway to be sure ? Maybe some kind of signature check from a mailing list 
or something where he announces he joined github ?

This is supposed to be his account: is it real ?

https://github.com/torvalds

If it is real then why does it not mention so on this page ?:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Bye for now,
  Skybuck =D

-- 
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/d440dc90-5331-446a-9c09-36b2e3630e80n%40googlegroups.com.

[git-users] Re: Official Linux Repository cannot be checked out because of illegal "aux" filenames on Microsoft Windows !

[skybuck2000]

Hello,

It's me again Skybuck Flying and I am reporting back on my linux kernel 
checkout experiments on Microsoft Windows 7:

I tried two methods, "normal clone" and "shallow clone".

During the normal clone I noticed how incredibly slow it was because of 
"resolving deltas" so I searched with google and came across this "shallow 
clone" trick which uses a depth parameter on the git clone command so I 
decided to try it at the same time as the normal clone and low and behold, 
the shallow clone was 10 times faster !

(I also inspected resource consumption and it's kinda weird, it's not 
really a max cpu bottleneck, neither a ram limitation or harddisk 
speed/latency/seek problem, most likely it's caused by xor-ing or computing 
sha1 hashes or maybe changes on top of changes on top of changes 
re-building objects, maybe the linux repository does not use snapshots or 
something where the files are stored in full after each year or something ? 
Don't know, there seems to be some confusion about this on stack overflow, 
how this technically exactly works, anyway)

However the shallow clone does show some more potential problems, this time 
with case-sensitivity of filenames, see below for the results:

Method 1 (Normal clone):

$ git clone https://github.com/SkybuckFlying/linux.git

(Still in progress)

Method 2 (Shallow clone):

$ git clone --depth 1 https://github.com/SkybuckFlying/linux.git

Results of Method 2 (Shallow clone):

new@new-PC MINGW64 /e/SourceCode
$ cd LinuxKernelShallowClone

new@new-PC MINGW64 /e/SourceCode/LinuxKernelShallowClone
$ git clone --depth 1 https://github.com/SkybuckFlying/linux.git
Cloning into 'linux'...
remote: Enumerating objects: 79577, done.
remote: Counting objects: 100% (79577/79577), done.
remote: Compressing objects: 100% (73582/73582), done.
remote: Total 79577 (delta 7208), reused 32402 (delta 5184), pack-reused 0
Receiving objects: 100% (79577/79577), 213.77 MiB | 8.08 MiB/s, done.
Resolving deltas: 100% (7208/7208), done.
Updating files: 100% (75027/75027), done.
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:

  'include/uapi/linux/netfilter/xt_CONNMARK.h'
  'include/uapi/linux/netfilter/xt_connmark.h'
  'include/uapi/linux/netfilter/xt_DSCP.h'
  'include/uapi/linux/netfilter/xt_dscp.h'
  'include/uapi/linux/netfilter/xt_MARK.h'
  'include/uapi/linux/netfilter/xt_mark.h'
  'include/uapi/linux/netfilter/xt_RATEEST.h'
  'include/uapi/linux/netfilter/xt_rateest.h'
  'include/uapi/linux/netfilter/xt_TCPMSS.h'
  'include/uapi/linux/netfilter/xt_tcpmss.h'
  'include/uapi/linux/netfilter_ipv4/ipt_ECN.h'
  'include/uapi/linux/netfilter_ipv4/ipt_ecn.h'
  'include/uapi/linux/netfilter_ipv4/ipt_TTL.h'
  'include/uapi/linux/netfilter_ipv4/ipt_ttl.h'
  'include/uapi/linux/netfilter_ipv6/ip6t_HL.h'
  'include/uapi/linux/netfilter_ipv6/ip6t_hl.h'
  'net/netfilter/xt_DSCP.c'
  'net/netfilter/xt_dscp.c'
  'net/netfilter/xt_HL.c'
  'net/netfilter/xt_hl.c'
  'net/netfilter/xt_RATEEST.c'
  'net/netfilter/xt_rateest.c'
  'net/netfilter/xt_TCPMSS.c'
  'net/netfilter/xt_tcpmss.c'
  
'tools/memory-model/litmus-tests/Z6.0+pooncelock+poonceLock+pombonce.litmus'
  
'tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+pombonce.litmus'

It seems there might still be some issues after the checkout. Apperently 
from the looks of it the source code is developed on a file system which 
allows files to exist with the same alphabet letters but differentiates 
between capitals and small letters, which is kinda weird to be frank.

And now git seems to be reporting that only one of them was checkout. So I 
suspect that one of each is missing and this may lead to compile/build 
problems on NTFS file systems ?!

Well at least now I can get an impression of what this linux kernel 
development is all about ! LOL =D wiee =D

Bye for now,
  Skybuck Flying.

-- 
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/36a1debd-3fe6-4044-a6fe-5b515585563fn%40googlegroups.com.

[git-users] What is/are the adventage of a git diff driver and/or git chuck headers ?

[skybuck2000]

While examining the documentation for git attributes I came across 
something intrigueing:

https://git-scm.com/docs/gitattributes

Defining a custom hunk-header 

The following built in patterns are available:

pascal suitable for source code in the Pascal/Delphi language. 

Defining an external diff driver

Here is also an example of somebody who set this up:

https://github.com/alexkaratarakis/gitattributes/blob/master/Pascal.gitattributes


What are the adventages of using custom chunk headers ? and custom diff 
drivers ?

One of my main interests in this is that it might be helpfull for 
implementing "splitting/merging" of files.

My current idea is to create a utility which merges splitted files back 
into a big one.
Then merge changes from original source back into big one.
Then use a second utility to split the big one back into splitted files.

The second utility needs to scan the big file for "headers". The first 
utility should insert these "headers".
Plus some links would need to be defined for example:
BigOne -> SmallA
BigOne -> SmallB
BigOne -> SmallC

So that both merge and split know how to do their work.

Perhaps git already has some of the features necessary to make this work.

Perhaps git already has a full feature that can work like this ?

If not then perhaps these chunk headers can help ? and perhaps git has some 
links inside of it ?

Is it possible to tell git that one big file is linked/splitted into 
multiple files with "plumbing commands" ?

I have not looked/studied at the git source codes but perhaps I will 
sometime in future.

Any hyperlink to git sources is also welcome in case it's hard to find with 
google or something :) Haven't tried yet.

I did try to find information about git diff drivers, not much out 
there...  same for git custom chunk headers... 

So some more information/help/tutorial/explanation about this and why it's 
usefull or what the adventages would be would be great !

Also any disadventages would also be interestng !

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/7e2d53ba-0172-4075-97c3-7e6bb5eece42n%40googlegroups.com.

[git-users] Uploading/Downloading local branch tracking information ?

[skybuck2000]

I have a script called: CreateAdvancedRepositoryTabbed.sh which can be 
downloaded here:

https://github.com/SkybuckFlying/PascalCoin

It uses git clone --mirror technique to download all the remote branches 
(which are local to the server/remote) and to re-create them locally.

Then the refs are updated in step 6 and re-fetched in step 7.

What I find weird about all descriptions/tutorial I have read so far on the 
internet is it is not explained how tracking information can be uploaded 
and re-downloaded ?!?

So apperently during a normal git clone... tracking information is setup 
for the master branch. 

Is this an effect of the git clone command simply running git branch 
--setup tracking information for master.

Or is there a way to upload "local tracking information" and then later 
re-download it later from the server.

As to auto-re-create local tracking information after download ?

If this is not possible then I guess my only other option is to re-run the 
git commands

git branch --set-upstream-to=origin/PascalCoinMaster PascalCoinMaster

I also tried the alternative:

git push -u origin PascalCoinMaster

Also had no effect when re-download/re-creating the repo on a different 
virtual machine.

This tracking information is still lost on this different virtual machine.

So far I have not used tracking feature that much but I do start to see 
advantages in powershell and others/bash it can alert me that there are 
commits on the server that need to be fetch/pulled to stay up to date and 
avoid costly re-bases or mergers... and also... it reduces the ammount of 
typing with tracking setup I can  just type:

git pull

instead of

git pull origin PascalCoinMaster

^ which is also becoming a bit annoying and tiredsome but ok.

Anyway re-setting all the branch tracking information I case I create a lot 
of these tracking branches would be a bit weird ?!?

Especially if later these branches are deleted/destroyed. I don't plan on 
doing that yet because I believe in keeping history intact/stored but my 
repo is a bit of a mess since I am just having with fun and getting into 
it... no main flow strategy yet or tagging strategy... just trying out 
things and branching whatever the fok I want :)

Anyway I am a bit surprised about this lack of re-downloading tracking 
information.

If it's really not possible ? (Which I doubt ? Maybe it can be done 
manually in some config or file ?)

Then I may have to request this as a next feature for GIT next 
versionssszzz !

Would be a cool feature to have if I can type for example:

git fetch branch-tracking-information.

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/11819f74-d82c-4e59-8784-749653040c48n%40googlegroups.com.

[git-users] bash echo ' and ( problem

[skybuck2000]

Script test.sh runs badly in git bash:

echo Let's start

and 

echo (convert blabla)

Creates problems when run:

./test.sh

Complains missing ' to terminate
Complains ( 

How to solve these problems for git bash echo ?!?!?!?

I tried

git echo "Let's start"

But problem remains.

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/43bb719d-f018-4932-b885-1db263db5bd0n%40googlegroups.com.

[git-users] Re: Creating attributes file automatically ?

[skybuck2000]

md command added to make this script work in ms-dos/cmd/windows/powershell 
too:
only tested in cmd.exe should work in powershell too:

echo Skybuck Flying Here !
echo
echo This script create a filter for this git repository
echo
echo 1. To turn 2 spaces into tabs on checkout
echo 2. To turn 1 tab into 2 spaces on commits
echo
echo For the following Pascal/Delphi file extensions:
echo
echo pas dpr dpk inc dfm xfm fmx lfm nfm dpkw
echo
echo This script requires GnuWin32 CoreUtils package to be installed.
echo 
echo Which can be found here:
echo http://gnuwin32.sourceforge.net/packages.html
echo and here:
echo http://gnuwin32.sourceforge.net/packages/coreutils.htm
echo
echo After installation its bin folder needs to be on the path environment
echo So that expand.exe and unexpand.exe can be found and executed.
echo
echo To run this script type: ./CreateSpacesToTabsFilter.sh
echo
md ".git/info"
mkdir .git/info 
echo "*.pas filter=tabspace2" > .git/info/attributes
echo "*.dpr filter=tabspace2" >> .git/info/attributes
echo "*.dpk filter=tabspace2" >> .git/info/attributes
echo "*.inc filter=tabspace2" >> .git/info/attributes
echo "*.dfm filter=tabspace2" >> .git/info/attributes
echo "*.xfm filter=tabspace2" >> .git/info/attributes
echo "*.fmx filter=tabspace2" >> .git/info/attributes
echo "*.lfm filter=tabspace2" >> .git/info/attributes
echo "*.nfm filter=tabspace2" >> .git/info/attributes
echo "*.dpkw filter=tabspace2" >> .git/info/attributes

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/72e0f31f-3e62-4202-89b3-7e4d6577a3b1n%40googlegroups.com.

[git-users] Re: Creating attributes file automatically ?

[skybuck2000]

Slightly better description to hopefully prevent any confusion. Note it's 
also important to add an carriage return/line feed at last line of script:

echo Skybuck Flying Here !
echo
echo This script create a filter for this git repository
echo
echo 1. To turn two spaces into one tab on checkout
echo 2. To turn one tab into two spaces on commits
echo
echo For the following Pascal/Delphi file extensions:
echo
echo pas dpr dpk inc dfm xfm fmx lfm nfm dpkw
echo
echo This script requires GnuWin32 CoreUtils package to be installed.
echo 
echo Which can be found here:
echo http://gnuwin32.sourceforge.net/packages.html
echo and here:
echo http://gnuwin32.sourceforge.net/packages/coreutils.htm
echo
echo After installation its bin folder needs to be on the path environment
echo So that expand.exe and unexpand.exe can be found and executed.
echo
echo To run this script type: ./CreateSpacesToTabsFilter.sh
echo
md ".git/info"
mkdir .git/info 
echo "*.pas filter=tabspace2" > .git/info/attributes
echo "*.dpr filter=tabspace2" >> .git/info/attributes
echo "*.dpk filter=tabspace2" >> .git/info/attributes
echo "*.inc filter=tabspace2" >> .git/info/attributes
echo "*.dfm filter=tabspace2" >> .git/info/attributes
echo "*.xfm filter=tabspace2" >> .git/info/attributes
echo "*.fmx filter=tabspace2" >> .git/info/attributes
echo "*.lfm filter=tabspace2" >> .git/info/attributes
echo "*.nfm filter=tabspace2" >> .git/info/attributes
echo "*.dpkw filter=tabspace2" >> .git/info/attributes

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/192b0aca-e8ef-4e75-9e57-82b053f1841bn%40googlegroups.com.

[git-users] Creating attributes file automatically ?

[skybuck2000]

Right now I am in the process of following this tutorial to auto-convert 
spaces to tabs:

https://sites.google.com/site/gibekm/programming/git/converting-between-tabs-and-spaces

I would like to automate step 3 so it could be placed in a repository 
creation batch file like

CreateAdvancedRepo.sh or so...

So my question is how to place a text string like:

" *. filter=tabspace2" 

into a new file and new directory like so:

.git/info/attributes 

>From experimenting and googling best way to do this seems to be:

new@new-PC MINGW64 /e/SourceCode/PascalCoinGit/PascalCoin (PascalCoinMaster)
mkdir NewFolder

new@new-PC MINGW64 /e/SourceCode/PascalCoinGit/PascalCoin (PascalCoinMaster)
echo "this is a line" > newfolder/file.txt

However echo can be tricky and might not do the more complex command above 
going to give it a try:

new@new-PC MINGW64 /e/SourceCode/PascalCoinGit/PascalCoin (PascalCoinMaster)
echo " *. filter=tabspace2" > newfolder/test.txt

OK So far so good, problem seems solved for now ! ;) =D

Going to give this auto conversion a try soon...

I see one little potential problem with this method, maybe the attributes 
file already existed, but in new repo problably not...

Perhaps:

echo "this is a line" >> newfolder/file2.txt

Might be more safe.

OK All seem to have worked and puts this line in a text file:
 *. filter=tabspace2

Tutorial text from link above:

"

It is very easy to convert between tabs and spaces automatically when 
committing and check-outing text files with GIT. GIT allows it with the 
attributes mechanism:

http://git-scm.com/book/ch7-2.html 


http://stackoverflow.com/questions/2316677/can-git-automatically-switch-between-spaces-and-tabs
 


To configure this behavior all you need is:

   1. Place 'expand' and 'unexpand' commands in your 'PATH' environment 
   variable. For Windows they are part of GnuWin32 CoreUtils package:
  1. http://gnuwin32.sourceforge.net/packages.html 
  

   2. Define needed GIT filter names. These are examples if you want tabs 
   locally and two or four spaces in the repository:
  1. git config --system filter.tabspace2.clean "expand --tabs=2 
 --initial"
 2. git config --system filter.tabspace2.smudge "unexpand --tabs=2 
 --first-only"
 3. git config --system filter.tabspace4.clean "expand --tabs=4 
 --initial"
 4. git config --system filter.tabspace4.smudge "unexpand --tabs=4 
 --first-only" 
  3. Apply settings to your local repository.
  1. Create .git/info/attributes file inside your local repository 
  directory and add following line(s) to it:
 1. *. filter=tabspace2
  2. Where  is file extension than will be filtered.
   4. If you have any changes, commit them and then checkout all files to 
   have filtered version on a disc:
  1. git checkout HEAD -- **
  
Nemerle

Things may be a little more complicated when you want to do the same with 
Nemerle source codes, because there is a risk that 'unexpand' command can 
corrupt files that are using indentation-based syntax. The solution is to 
use script that expands/unexpands only files with non indentation-based 
syntax. You can copy tabs_nemerle.sh script to the bin directory of git and 
configure filters that way:
git config --system filter.tabspace2.clean "tabs_nemerle.sh 2 expand"git 
config --system filter.tabspace2.smudge "tabs_nemerle.sh 2 unexpand"
"

Bye,
  Skybuck.

(Somehow my e-mail is screwed up but ok)

-- 
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/342137bb-a47f-4b33-bbc2-e6e2f77f6edbn%40googlegroups.com.