From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Warner Losh <imp@bsdimp.com>
Cc: Rudi Blom <rudi.j.blom@gmail.com>, coff <coff@minnie.tuhs.org>
Subject: Re: [COFF] What is your prompt?
Date: Mon, 27 Dec 2021 20:25:45 +0100 [thread overview]
Message-ID: <20211227192545.QmevV%steffen@sdaoden.eu> (raw)
In-Reply-To: <CANCZdfrKFTjWnNGcZBTBfZ9e379VwjhNJK3Z8mLJR9dKLOj4SA@mail.gmail.com>
Warner Losh wrote in
<CANCZdfrKFTjWnNGcZBTBfZ9e379VwjhNJK3Z8mLJR9dKLOj4SA@mail.gmail.com>:
|On Mon, Dec 27, 2021 at 11:44 AM Steffen Nurpmeso <steffen@sdaoden.eu>
|wrote:
|> Warner Losh wrote in
|> <CANCZdfoP6bkJCMTD96p=iEH8YP9cq1vX9TfXDASu0egmPYGVfQ@mail.gmail.com>:
|>|On Sun, Dec 26, 2021, 2:18 PM Theodore Ts'o <tytso@mit.edu> wrote:
|>|> I keep a private git repo on one of my machines, so when I get a HOST
|>|> account, I run a comand like this:
|>|>
|>|> % git clone ssh://tytso@example.com/home/tytso/repos/dotfiles .
|>|
|>|I have symlinks to all my files. I also have special hooks that I run per
|>|os and per host to pull in different configs when needed. Though in
|>|recent years I've not needed it much. I used to do a lot for work like
|>|this, but these days work envs are close to my home env, so there is
|> little
|>|point.
|>|
|>|I've been doing this since RCS days across 5 different SCMs... git makes
|>|oopses so rare that the paranoia below seems overkill. Though for other
|>
|> Oh yes, i could not agree more. I never tried bitkeeper ;), but
|> even after eleven years of git (~/calendar (symlink) just told me
...
|> 12/24 Beschließe öffentliche Projekte mit GIT zu managen (2010)
...
|The first years of git were interesting times to be using it. After that
|it's been rock solid, especially relative to all the other tools out there.
"rebase --onto" never really worked for me until it then did, but
it took long. They reversed the output of rev-parse at some time,
i test for version 1.8 for the switch. The garbage collect memory
window limit maybe now works .. and garbage collection took longer but
required less memory in earlier times, i always see it on the
OpenCSW.org cluster which uses git 2.4, 1.7.10.3 and what
else, but the plan to build on old one just for gc i never put in
practice; whether that today would still work, i do not know
either, no hash but SHA-1 here still, however.
I hated it bailed on breaking network connections, i do not know
whether they fixed it, i am now behind datagram based VPN, and
that "heals" that problem for me, practically always, luckily. It
is a pain with a bad internet connection when huge downloads then
break after say hundreds of megabytes, and cannot be restarted at
the time it bailed. On the other hand i never tried to fix it,
not even locally.
No breakage here, never. Wow.
| I have something similar to the .local stuff Ted does. In fact, I used to
|use exactly that pattern. However, I've taken to doing that via symlinks
|to the host name (so foo.host with multiple ones symlinked to the
|master if it comes to that). That way I could keep my local changes
|in version control... One to many client machines crashing and losing
|stuff in my past...
Yeah. No. :) (But for one lost backup encryption key that almost
broke me and anyway ate some really good work i was/am prowd of.)
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-12-27 19:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 2:50 Rudi Blom
2021-12-25 4:40 ` Theodore Ts'o
2021-12-25 17:39 ` Steffen Nurpmeso
2021-12-25 18:28 ` Grant Taylor via COFF
2021-12-25 19:14 ` Steffen Nurpmeso
2021-12-26 3:44 ` Grant Taylor via COFF
2021-12-25 23:19 ` Greg 'groggy' Lehey
2021-12-25 23:43 ` Steffen Nurpmeso
2021-12-26 21:18 ` Theodore Ts'o
2021-12-26 21:33 ` Warner Losh
2021-12-27 1:33 ` Theodore Ts'o
2021-12-27 2:52 ` Rudi Blom
2021-12-27 3:43 ` Greg 'groggy' Lehey
2021-12-27 4:06 ` Rudi Blom
2021-12-27 4:12 ` Greg 'groggy' Lehey
2021-12-27 4:28 ` Rudi Blom
2021-12-27 18:44 ` Steffen Nurpmeso
2021-12-27 18:55 ` Warner Losh
2021-12-27 19:07 ` Grant Taylor via COFF
2021-12-27 19:25 ` Steffen Nurpmeso [this message]
2021-12-27 18:37 ` Steffen Nurpmeso
2021-12-26 3:29 ` Grant Taylor via COFF
2021-12-26 3:54 ` Greg 'groggy' Lehey
2021-12-26 5:27 ` Grant Taylor via COFF
-- strict thread matches above, loose matches on Subject: below --
2021-12-23 6:59 [COFF] What is your prompt? (was: ksh88 source code?) Andy Kosela
2021-12-24 17:17 ` [COFF] What is your prompt? Grant Taylor via COFF
2021-12-26 22:17 ` Mike Markowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211227192545.QmevV%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=coff@minnie.tuhs.org \
--cc=imp@bsdimp.com \
--cc=rudi.j.blom@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).