On 10/7/23 01:51, to...@tuxteam.de wrote:
On Fri, Oct 06, 2023 at 01:44:34PM -0700, Mike Castle wrote:
Something I played with recently was
https://packages.debian.org/stable/vcs/git-filter-repo
Yes, it does work. My typical use case is when someone has put a
password in the repo you don't eve
On Fri, Oct 06, 2023 at 01:44:34PM -0700, Mike Castle wrote:
> Something I played with recently was
> https://packages.debian.org/stable/vcs/git-filter-repo
Yes, it does work. My typical use case is when someone has put a
password in the repo you don't even want to have in the history.
But you ar
Something I played with recently was
https://packages.debian.org/stable/vcs/git-filter-repo
But you definitely want to run tests on real data before you decide
that deleting old data saves your anything, particularly with respect
to time.
If git is so efficient at storing this kind of data, then
>> `git gc` does delete the old data (if it's not reachable any more).
> And it is very expensive. My point exactly.
It's fairly expensive indeed, but it's usually an operation that is not
very time-sensitive: it can usually be delayed to a convenient time, and
you can run it infrequently and as
Stefan Monnier (12023-10-06):
> `git gc` does delete the old data (if it's not reachable any more).
And it is very expensive. My point exactly.
> BTW, if you want to (ab)use a Git repository to do backups, you should
> definitely look at `bup`.
Thanks, it might be exactly what I am looking for.
> Have you tried? The very principle of Git makes it necessary, to remove
> or update old data, to rewrite the whole subsequent history.
> Furthermore, it is done by creating a new branch, the original data is
> not actually deleted.
`git gc` does delete the old data (if it's not reachable any mor
john doe (12023-10-06):
> Please elaborate on why Git is so bad at removing data from a single
> repository?
Have you tried? The very principle of Git makes it necessary, to remove
or update old data, to rewrite the whole subsequent history.
Furthermore, it is done by creating a new branch, the or
On 10/6/23 13:26, Nicolas George wrote:
john doe (12023-10-06):
I do not understand why you would want multiple repos, to me this looks
like this would fit the bill for a Git branching workflow.
Please elaborate. How do you work around the fact that Git is terrible
at removing data with a sing
Max Nikulin (12023-10-06):
> I have no idea if it is possible to do it in place, but "git clone" and "git
> fetch" have the --depth option. So you can specify how many last commits you
> would like to have in the cloned repository. Using "git rebase
I know. They only allow to keep the last commits
john doe (12023-10-06):
> I do not understand why you would want multiple repos, to me this looks
> like this would fit the bill for a Git branching workflow.
Please elaborate. How do you work around the fact that Git is terrible
at removing data with a single repository?
Regards,
--
Nicolas
On 10/6/23 11:14, Nicolas George wrote:
Hi.
There is a project I have that requires some scripting, but I am
wondering if somebody already did something similar and there is a
package that I can just apt-get install.
The idea is to use Git to store backups of text files that change rather
rarel
On 06/10/2023 16:14, Nicolas George wrote:
Unfortunately, Git is very bad at removing old data
I have no idea if it is possible to do it in place, but "git clone" and
"git fetch" have the --depth option. So you can specify how many last
commits you would like to have in the cloned repository.
Hi.
There is a project I have that requires some scripting, but I am
wondering if somebody already did something similar and there is a
package that I can just apt-get install.
The idea is to use Git to store backups of text files that change rather
rarely or not a lot, because Git is very effici
13 matches
Mail list logo
