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

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 "

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

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/[/]/\

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

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

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

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/a

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

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 bot

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

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 slig

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

> > 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 > | A

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

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

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

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 "

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

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 th

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

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 hap

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

>>> "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. -- You received this message because you are subscribed to the Google Gr

[git-users] Re: git grep --no-index

printf 'bar\nboo\nbzz\n' > foo git grep --no-index --files-with-matches --all-match -e -bar -e boo -e bzz -- foo cd ../ git grep --no-index --files-with-matches --all-match -e -bar -e boo -e bzz -- git/foo git grep --no-index --files-with-matches --all-match -e -bar -e boo -e bzz git

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

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

[git-users] 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

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

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)

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

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 u

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

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 becau

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

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 th

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

LISTEN UP YOU MOTHERFUCKERS I JUST CREATED THIS FOLDER ON MY WINDOWS: PascalCoinGit(For Copy&Paste 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 WO

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

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.