Re: How to recovery from a file accidentally committed twice?

2021-08-17 Thread Klaus Ethgen
Am Di den 17. Aug 2021 um 19:06 schrieb Marc Haber:
> one second of not paying attention did it, and I accidentally committed
> a file that is in one vcsh-repository, bin/foo to a second vcsh
> repository. Now both repos are fighting about that file. vcsh bar rm
> bin/foo just took the fight to another limit?
> 
> How do I recover, telling the wrong repository to completely forget about the 
> file?

vcsh bar rm --cached bin/foo

Gruß
   Klaus
-- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16    Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C


signature.asc
Description: PGP signature
___
vcs-home mailing list
vcs-home@lists.madduck.net
https://lists.madduck.net/listinfo/vcs-home


Re: Managing git remotes

2016-03-07 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Am So den  6. Mär 2016 um 18:06 schrieb Christopher Baines:
> just fixup?), so it does not really work. I also want 2 standard remotes
> for most of the repositories, but that would require adding different
> fixup lines to all of repository definitions.

Well, Maybe not for the past, but why don't you use git
url..insteadOf feature? That allows you to use kind of alias for
your Repos and if they change, just change the alias. I used to have
short alias for my main repositories.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen <kl...@ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJW3VGfAAoJEKZ8CrGAGfasDSsL+wWV5qotEBQU1hOc98PeudcG
UhJ/DXuTVVgnqeopyXFXffkwuxr97fLsVQk9MS8l6T7TigPCKUVDAqxjIKq8dsUB
nXQzkU0Mo1s9NznGLnyyq8/CMQ6ZfuwR/weGaFpFMGOk30GPtJoZdMWL0Klu90R+
MlPl2aDtrU3WRsZcTlqoWafmlqv2jUJWYr6ANMnJvrfCxP8ebTswLXk3eCDZN3dT
ZE4nM+X345+o6HQRyjoZJMy+/IEeL1a2bPKvjD9BNGGwEXBoZXKvPfLGC2XIUQoF
sGzmAWdrn1x3l3DNKslRkyVrRkUsK+CuyQScAcQiA626UKI8JJN/ZFr+2P00dVHB
zUyCqhK9FCLA2pi2dma1UXKN/cu9qtXmrOFg79QaGcA6ujMpb3rfhYRtDehJuacn
rZJgyqu2MWal+gtE8MdIDPd38cvaWVVxmcTj4AS6HK2kLtBAgcFrElU3Re4rxFoY
/Ng3K2HozlCe33j9AN2hdJyV8okoEn52ZjDzHvvsJQ==
=m5eM
-END PGP SIGNATURE-
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home


Re: more git-annex plumbing

2012-04-16 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

Am Mo den 16. Apr 2012 um 10:59 schrieb Thomas Koch:
 I have a few things that I'd like to do with git-annex but that are hard 
 because git-annex does not expose internal plumbing commands. I intend to 
 start a list of such commands here with possible use cases:
 
 - calculate checksum of a file
 - doesAnnexHasChecksum?
 - doesAnnexHasFile?
 
   Useful to deduplicate files from many old CD backups
 
 - checksum to path
 - move file into annex

Especially the second last I was searching for many times. I did this
with some pipe doing readlink and grep.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQGcBAEBCgAGBQJPjEZsAAoJEKZ8CrGAGfasz5UMAKobMuG8eVaqOdA/TDjsUg5E
pTDnAcv91dgUDjLn/lPl6Si2uDpDqhyBX56qHShRaeQ5z17Wps1t6ij5srs2c1BY
mX0kvKbrQyPB4czOrCX9fISjTivjCoxbBbgMe9IdH0Nbz4Ul9vB60IuhUnZ47Dlc
83X4sc+s9ODoPvCEMI+OKT6rr/ImRgeE9a/pglUasjNCukipolcB7V3RIaitnC3q
xS4Cz62/oWoy4cIKbpSvNtiP6bRaZP6WtVxJxr526L+/WEuzXjbb8nSWnk4j81R/
A7PGANXZryrUkVbj3zCsZO37evfMtFQpf/FT8I1rkvpOpFzHqW+IFOt8QOUtcW9/
CWykqsO92Z8Q1YWtTbv7oRC59kAKhpMjz3SbDmI5GZyRAEHW14f99FRDQsLg5WkN
oFsCmJbGkRXB0zTM1vuPGsooYzIHW1NUppijm233aAzlLMR17lHKhp9jzqgTdhbI
6hxvcWVjpBZwA/0X3ZYhy8TGvWNfwYu2NfZS+vBlSg==
=2Yca
-END PGP SIGNATURE-
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home


Spaces in remotes and git annex

2012-01-05 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
NotDashEscaped: You need GnuPG to verify this message

Hi,

I seems to be predestined to find strange problems. ;-)

Today I cloned a remote git annexed repository that has a space in path.
With git I have to use one backslash instead of three that are needed in
scp. Now I tried to get a document from that repository and failed as
git-annex seems to use scp and need all three backslashes.

Is there any way to work around that problem?

Regards
   Klaus
-- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQGcBAEBCgAGBQJPBdp3AAoJEKZ8CrGAGfasaa4L/iYWz+qRsa2RiVt0RRWIV4X2
ABm2tFFHJ0pyP/Zguea8omLPYvg5xf1qpIUiKZB1A3DerbxN6IdwgytfXfDX3aKz
QSHU0VisgjS2JXxajPXygNqYex8Obomcjj/n/gR9abRInPDwOqllLpL6vVCMzDd+
/xDH53Yocckorvq+oIKUKl8JGZSsyY85hm+Jbveac91RYchTfvqajCBhO/zCVjXl
JXwTiovtr3rNQPbf3rxh0XLejGVvPwNWfw3RAz1G8TgKmyzDP1IIQzuVcN5/le9z
lq32ve5UaroWQwZHBwsXHVObBV42eQpktV+VPDSOCS8SnIoXNbpYvR4GhxF1Rz6x
uuGCy128LxW6xjksxqbjlnFpYMDaiz7ZuKfK6IolU/LrQu0k3b5JJBp+1fJ3tCBB
zX4D/TMjJJ0uf1dUfXCrGBG9zaYf4rH24R12WORz8rM6wHhkEEbYFXufD2TWnH6f
X6ZH+HZXa/SSAKzd9J1WrR9TwamWHIC+vc7ni9Dw2w==
=1f+I
-END PGP SIGNATURE-
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home


Re: Lost Repository Was: Removing git-annex Repo

2011-12-05 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Mo den  5. Dez 2011 um 17:19 schrieb Joey Hess:
 Klaus Ethgen wrote:
   Can you check out the git-annex branch and run git-log on uuid.log, 
   and see what the most recent change to it looked like?
  
  It is an update. After that I revert this update and the next time it
  will purged again.
 
 It sort of sounds as if you are checking out the git-annex branch,
 manually editing and committing a file, and seeing git-annex revert
 that change.

Well, after the Bug happens several times I started to do the following
after git-annex removed the occurrences:
   git checkout git-annex
   git cherry-pick id # This id is the first time I fixed it by hand
   git add trust.log uuid.log
   git commit -m Correcting update
   git checkout master

The patch looks somethink like:
   diff --git a/trust.log b/trust.log
   index xxx..xxx 100644
   --- a/trust.log
   +++ b/trust.log
   @@ -1 +1,2 @@
---- 1 timestamp=1322867090.765867s
   +---- 0 timestamp=1322867165.394761s
   diff --git a/uuid.log b/uuid.log
   index xxx..xxx 100644
   --- a/uuid.log
   +++ b/uuid.log
   @@ -1,2 +1,3 @@
   ----- Backup timestamp=1322866827.929813s
---- Master timestamp=1322866770.445515s
   +---- Backup timestamp=1322866827.929813s
   +---- Clone timestamp=1322867722.827595s

Which is the revert of this two files.

 That's expected behavior actually..
 http://git-annex.branchable.com/internals/ explains why. 

Sorry, no it don't. I do not want to modify the git-annex branch as I
know it is internal. But the situation gives me no other choice than to
revert it every and every time.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQGcBAEBCgAGBQJO3PVpAAoJEKZ8CrGAGfasAPcL/2G12mXQWQcNaDO6tEdL7hkJ
CM5IA8xnxN4cOIWry3YbfDePwQ4Q3/rPnCEj/epGP7QIYB+tatPjJCCz+2ivprc7
GyZtih+C8cwYpad/T/QKEEAM2txMR2uy2kkGy43aFaCN2YRC/2KDmK5ePfxgcRTJ
W+U5VyNu8Aury73WzNGc41e8R/Uple8QZz/r9fvP5c23MtNB83229cjMNBauw4Q6
IHuM0tBNDSY22rZ0MG7WRFgtzgPOZjGsShMVn1TJFpelTheOsCtc0GVjkbwVaGrF
IND2Vo23kBFBlc6vy7g99lra7qAoAZxptfGbqZaMKEWXYVmAMiCB+KiBYE5CcH58
2e4sRbPj2xkVITD9RNlWrH7e/amBpf1w5a+i/gNmHMAGYvX0vYS2abwz+FdwqoQ2
ALhycZFig3kmYlDSw+64lS98j9TwAXdZ2IoBCwnJHRZrbrOLhcfBpmncZRW9TRa6
bW56MR5zZUzMpq8L4xtacmxKputo1WGsNhWXftpOGA==
=uWye
-END PGP SIGNATURE-
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home


Removing git-annex Repo

2011-12-02 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi all,

is there a other way than git checkout git-annex; sed -i -e
'/hash/d' **/*(.); git commit -a; git checkout master to remove a
repository completely from annex knowledge?

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQGcBAEBCgAGBQJO2RUHAAoJEKZ8CrGAGfasWwIL/i35UgG7tAiAJxRRnqgRuAZh
HuyA/B7eTGryRBfO8bHPBpShZhgkByuJU6FwEZtMpLaa6pIkQ9pOdD/vu+zrpJ2L
3Q2VHjtyCHsnsrKjH7qrA2PwQ88tG1X/8sBhUwwLWW9lUNAXdRZIEEelytHFj49c
RR46/8s0KdkhFcsFUUqR6emf+JQDg4n8UguMUM2efO5JMzYVeMZs7EqlOHqjaasa
yIS5+z+jHfZT4prpX6CI07+5QkJfdzGl+V2S0ex4KsB1DkvhmIGZ3Yi2CLIKs0A/
1t2sCbyw/VhGMU+qxJCV2hiZ9LLi/oMy01IA+8x7j/2AU2axqiuMxify+cKz+F/s
rHwYnoKE1BCaOkbsEynR1wpu5I8YoW4fWf4PUMiys8uBILeVW3ArK5VX6pQFg7oU
dd3B1wrRd8OZA+z1b5PK+pmd5HsRS2ipl9gCtRqtlckzscdsBE8DMxgPMA8gwV5F
dzxd4geKfXQDOUsPND75CXvkr3PR9S/v5ZQmd0Lhjg==
=ErBb
-END PGP SIGNATURE-
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home


Re: Removing git-annex Repo

2011-12-02 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hiho,

Am Fr den  2. Dez 2011 um 21:18 schrieb Joey Hess:
 Klaus Ethgen wrote:
  is there a other way than git checkout git-annex; sed -i -e
  '/hash/d' **/*(.); git commit -a; git checkout master to remove a
  repository completely from annex knowledge?
 
 Well, that doesn't actually work;

I felt it.

 if you do that and then pull a independantly changed git-annex branch
 from a remote, the auto-union-merge will then add back all the lines
 you removed.

Not only that, also a git annex fsck will bring it back. But I wonder
where it gets the description and ID of the old remote.

 Marking the repository untrusted is the usual way.

I red about. But I want to wipe out the whole repository and don't want
to have inherited waste.

And yes, I can do the cleanup on all remotes too.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQGcBAEBCgAGBQJO2TsMAAoJEKZ8CrGAGfasgcwL/2uwSDto2z2kOzfhrDq67812
2SsW3SM+3aFX2j7jCSCw2hm0Pk0Dx5J2vuOge8qu2fk9yStxVB/DpvwZZQLn73PW
Pha993XxHCbPxj+IvQA+pYbFZJ5Chq7GQdhrlfLQp1/Y+Y04FVvsVfLZzNoBghSC
HMSejI3vINaL1nyVkgJ0QDagUpNmcNeFsqoDJA/6wCne3EbypoItYZGXNJWWj6QH
RXe1ioMynUYo8B5lt3e6PN11w8tU1qqhOIeVODe8oqmgU21dEer/wkxRXlpkmPsJ
0PoJvDWYSVhBdER54+mzculeqTO/NHXjMAb8H9J0VNylnUWyf2s1S27r+Vu22RlA
IufcqGL5HuetkUgtZkXtIpk+zvLOF7yjxurX6unECFeJtZSYSRg+9b1SM5pFVJct
0glqEV9RK8iicCZmn3MmA+KUk1I6TI4wd6SjPbYHSBWlOT8fjjRa9+H/ouoJWBlI
6eKupbuzrAcDd5s8QE8hznAheuyRslz6+ofoX4D0dA==
=6Fqo
-END PGP SIGNATURE-
___
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home